RE: L4 Pistachio Build Environment
Jan Stoess <[email protected]> Mon, 11 Jun 2012 07:48:07 +0000
| Newsgroups | gmane.comp.micro-kernel.l4.l4ka.general |
|---|---|
| Message-ID | <[email protected]> |
--_000_0453D4730CA16449B61476A072CC48BC0EEA51E3i30s6osukade_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Ashford, No, there is no recommendend build environment, most gcc/binutils combinat= ions should just do. We do build tests with various toolchains, have a look= at http://www.l4ka.org/98.php. FWIW, we found recently out that with the m= ost recent gcc toolchain (4.6), there are seem to be problems for which we = don't have a fix yet. However, the older ones should actually do. Regarding the IRQ re-enablement problem: have you sent an acknowledgement I= PC? If so, I'd look into L4 trace points and the associated tracebuffer (kd= b menu entries 'r' and 'y') to find out what's going wrong. It might indeed= be a kernel bug, but I'd always be suspicious with the user-level code as = well. -Jan -- Dr. Jan Stoess, KIT System Architecture Group From: [email protected] [mailto:[email protected]= uhe.de] On Behalf Of Ashford Nichols Sent: Monday, May 28, 2012 5:36 PM To: [email protected] Subject: L4 Pistachio Build Environment Is there a recommended build environment to build the L4 pistachio Microker= nel? I have tried building it on my system and most times it builds properl= y and runs well on QEMU, but when I try to boot it on my system, (using the= floppy drive) it doesn't work quite like it should. One such case was with= the IRQ. I tried capturing and handling keyboard interrupts, but for some = reason the interrupt is never re-enabled. The system I am using is below: CPU - Intel Pentium 4 1.80GHz RAM - 768MB OS - Opensuse 11.4 GCC Version - 4.12 L4 Pistachio Version: l4ka-pistachio-dd624dd -- Ashford --_000_0453D4730CA16449B61476A072CC48BC0EEA51E3i30s6osukade_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif";} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Hello Ashford,<o:p></o:p>= </span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">No, there is no rec= ommendend build environment, most gcc/binutils combinations should just do.= We do build tests with various toolchains, have a look </span><span style=3D"font-size:11.0pt;font-family:"Calibri",&quo= t;sans-serif";color:#1F497D">at </span><span style=3D"font-size:11.0pt;font-family:"Calibri",&quo= t;sans-serif""><a href=3D"http://www.l4ka.org/98.php">http://www.l4ka.= org/98.php</a>.<span style=3D"color:#1F497D"> FWIW, we </span></span><span style=3D"font-size:11.0pt;font-family:"Calibri&quo= t;,"sans-serif";color:#1F497D">found recently out that with the m= ost recent gcc toolchain (4.6), there are seem to be problems for which we = don’t have a fix yet. However, the older ones should actually do.</span><span style=3D"font-size:11.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Regarding the IRQ re-enab= lement problem: have you sent an acknowledgement IPC? If so, I’d look= into L4 trace points and the associated tracebuffer (kdb menu entries ‘r’ and ‘y’) to find out what’s goin= g wrong. It might indeed be a kernel bug, but I’d always be suspiciou= s with the user-level code as well. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">-Jan <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Ca= libri","sans-serif";color:black">--<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:"Ca= libri","sans-serif";color:black">Dr. Jan Stoess, KIT System = Architecture Group<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in = 4.0pt"> <div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"= ;Tahoma","sans-serif"">From:</span></b><span style=3D"font-s= ize:10.0pt;font-family:"Tahoma","sans-serif""> l4ka-bou= [email protected] [mailto:[email protected]] <b>On Behalf Of </b>Ashford Nichols<br> <b>Sent:</b> Monday, May 28, 2012 5:36 PM<br> <b>To:</b> [email protected]<br> <b>Subject:</b> L4 Pistachio Build Environment<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Is there a recommended build environment to build th= e L4 pistachio Microkernel? I have tried building it on my system and most = times it builds properly and runs well on QEMU, but when I try to boot it o= n my system, (using the floppy drive) it doesn't work quite like it should. One such case was with the IRQ. I tr= ied capturing and handling keyboard interrupts, but for some reason the int= errupt is never re-enabled. The system I am using is below:<br> <br> CPU - Intel Pentium 4 1.80GHz<br clear=3D"all"> RAM - 768MB<br> OS - Opensuse 11.4<br> GCC Version - 4.12<br> L4 Pistachio Version: l4ka-pistachio-dd624dd<br> <br> -- <br> Ashford<o:p></o:p></p> </div> </div> </body> </html> --_000_0453D4730CA16449B61476A072CC48BC0EEA51E3i30s6osukade_--