virtex uImage and serial ports

virtex uImage and serial ports

[Joshua Lamorie]

Gidday there,=0A=0AI am trying to get 2.6.27(ish) running on my custom Virt=
ex-II Pro platform (I call it Q5).  I already have many years of running 2.=
4.26 and booting from u-boot.=0A=0AThe problem is getting the console runni=
ng.  I have a device tree blob built and loaded into memory, and by peeking=
 at __log_buf I can see that it is reading this okay (i.e. it is correctly =
finding my interrupt controller).  However, by the time it goes to mount th=
e ramdisk as root, it complains that there is no console.=0A=0AI'm fairly c=
ertain /chosen has stdout pointing to the correct UART, and the console arg=
uments are ttyS0,115200.=0A=0AIn looking through the code however, I cannot=
 figure out how the uImage code actually initializes the serial-ports for t=
he XILINX_VIRTEX_GENERIC_BOARD.  As I understand it, the only place where s=
erial_console_init is called, is within platform_init, and this isn't calle=
d for uImage.=0A=0ASo, three questions.=0A=0A1) How is the serial driver su=
pposed to know where the platforms serial ports are?=0A=0A2) If I wanted to=
 scrap u-boot and just copy kernel/ramdisk/dtb to memory, which kernel make=
 target should I use?  dtbImage, simpleImage?=0A=0A3) What is the best, mos=
t modern image to build that should be used by u-boot?=0A=0AThanks in advan=
ce=0A=0AJoshua=0A=0Ap.s. I've been trying with kernel.org mainline, xilinx =
git and denx ELDK xenomai (2.6.24).  U-boot is built from latest git source=
.  DTS file built from XPS 9.1i with latest service packs, and turned into =
DTB with latest dtc source from git.=0A=0A=0A-- =0AXiphos Technologies=0A(5=
14) 847-9474 x227=0A(514) 848-9644 fax=0A=0Awww.xiphos.com=0A______________=
_________________________________=0AThe information transmitted is intended=
 only for the=0Aperson or entity to which it is addressed and may contain=
=0Aconfidential and/or privileged material.  If you have=0Areceived this in=
 error, please contact the sender and delete=0Athis communication and any c=
opy immediately. Thank you.=0A=0A

RE: virtex uImage and serial ports

[John Linn]

Hi Joshua,

Have you looked at our wiki site at http://xilinx.wikidot.com as we
quite a bit of information there.

The ML405 board is a V2Pro chip so it should be pretty close to what you
want using the default kernel config for virtex4.

I haven't tested the console at 115,200 as I use it at 9600.  Shouldn't
be a problem, but may not hurt to stay at 9600 to get it working.

There are pages on the wiki about using u-boot with the kernel also as
it sounds like that's what you're doing.

Thanks,
John


> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-embedded-
> bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Joshua Lamorie
> Sent: Wednesday, December 24, 2008 3:48 PM
> To: linuxppc-embedded@ozlabs.org
> Subject: virtex uImage and serial ports
> =

> Gidday there,
> =

> I am trying to get 2.6.27(ish) running on my custom Virtex-II Pro
platform (I call it Q5).  I already
> have many years of running 2.4.26 and booting from u-boot.
> =

> The problem is getting the console running.  I have a device tree blob
built and loaded into memory,
> and by peeking at __log_buf I can see that it is reading this okay
(i.e. it is correctly finding my
> interrupt controller).  However, by the time it goes to mount the
ramdisk as root, it complains that
> there is no console.
> =

> I'm fairly certain /chosen has stdout pointing to the correct UART,
and the console arguments are
> ttyS0,115200.
> =

> In looking through the code however, I cannot figure out how the
uImage code actually initializes the
> serial-ports for the XILINX_VIRTEX_GENERIC_BOARD.  As I understand it,
the only place where
> serial_console_init is called, is within platform_init, and this isn't
called for uImage.
> =

> So, three questions.
> =

> 1) How is the serial driver supposed to know where the platforms
serial ports are?
> =

> 2) If I wanted to scrap u-boot and just copy kernel/ramdisk/dtb to
memory, which kernel make target
> should I use?  dtbImage, simpleImage?
> =

> 3) What is the best, most modern image to build that should be used by
u-boot?
> =

> Thanks in advance
> =

> Joshua
> =

> p.s. I've been trying with kernel.org mainline, xilinx git and denx
ELDK xenomai (2.6.24).  U-boot is
> built from latest git source.  DTS file built from XPS 9.1i with
latest service packs, and turned
> into DTB with latest dtc source from git.
> =

> =

> --
> Xiphos Technologies
> (514) 847-9474 x227
> (514) 848-9644 fax
> =

> www.xiphos.com
> _______________________________________________
> The information transmitted is intended only for the
> person or entity to which it is addressed and may contain
> confidential and/or privileged material.  If you have
> received this in error, please contact the sender and delete
> this communication and any copy immediately. Thank you.
> =

> =

> =

> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded


This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.

RE: virtex uImage and serial ports

[Joshua Lamorie]

Gidday John,=0A=0AThanks for the pointer.  I think I have already gone thro=
ugh every possible page on the wiki, without finding my answer.  There are =
some great pointers however, such as http://xilinx.wikidot.com/debugging-ke=
rnel-boot-problems.  =0A=0AAs far as I can tell, if I do 'make uImage', the=
re is no code built into vmlinux that will parse the device tree and set up=
 the serial ports (at least as far as I can see with objdump -S).  When it =
boots, there is no console output and __log_buf doesn't show any serial por=
ts detected during the initialization of the serial driver.=0A=0AWhich lead=
s to my question, how does the 8250 serial driver get the information about=
 the attached serial ports from the dtb?  Which part of the code parses the=
 dtb, finds the "ns16550" and updates/builds the platform_device informatio=
n for the 8250 serial port driver?=0A=0AJoshua=0A=0AOn Tuesday, 30 December=
, 2008 13:16, "John Linn" <John.Linn@xilinx.com> said:=0A=0A> Hi Joshua,=0A=
> =0A> Have you looked at our wiki site at http://xilinx.wikidot.com as we=
=0A> quite a bit of information there.=0A> =0A> The ML405 board is a V2Pro =
chip so it should be pretty close to what you=0A> want using the default ke=
rnel config for virtex4.=0A> =0A> I haven't tested the console at 115,200 a=
s I use it at 9600.  Shouldn't=0A> be a problem, but may not hurt to stay a=
t 9600 to get it working.=0A> =0A> There are pages on the wiki about using =
u-boot with the kernel also as=0A> it sounds like that's what you're doing.=
=0A> =0A> Thanks,=0A> John=0A> =0A> =0A>> -----Original Message-----=0A>> F=
rom: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org=0A> [mailt=
o:linuxppc-embedded-=0A>> bounces+john.linn=3Dxilinx.com@ozlabs.org] On Beh=
alf Of Joshua Lamorie=0A>> Sent: Wednesday, December 24, 2008 3:48 PM=0A>> =
To: linuxppc-embedded@ozlabs.org=0A>> Subject: virtex uImage and serial por=
ts=0A>>=0A>> Gidday there,=0A>>=0A>> I am trying to get 2.6.27(ish) running=
 on my custom Virtex-II Pro=0A> platform (I call it Q5).  I already=0A>> ha=
ve many years of running 2.4.26 and booting from u-boot.=0A>>=0A>> The prob=
lem is getting the console running.  I have a device tree blob=0A> built an=
d loaded into memory,=0A>> and by peeking at __log_buf I can see that it is=
 reading this okay=0A> (i.e. it is correctly finding my=0A>> interrupt cont=
roller).  However, by the time it goes to mount the=0A> ramdisk as root, it=
 complains that=0A>> there is no console.=0A>>=0A>> I'm fairly certain /cho=
sen has stdout pointing to the correct UART,=0A> and the console arguments =
are=0A>> ttyS0,115200.=0A>>=0A>> In looking through the code however, I can=
not figure out how the=0A> uImage code actually initializes the=0A>> serial=
-ports for the XILINX_VIRTEX_GENERIC_BOARD.  As I understand it,=0A> the on=
ly place where=0A>> serial_console_init is called, is within platform_init,=
 and this isn't=0A> called for uImage.=0A>>=0A>> So, three questions.=0A>>=
=0A>> 1) How is the serial driver supposed to know where the platforms=0A> =
serial ports are?=0A>>=0A>> 2) If I wanted to scrap u-boot and just copy ke=
rnel/ramdisk/dtb to=0A> memory, which kernel make target=0A>> should I use?=
  dtbImage, simpleImage?=0A>>=0A>> 3) What is the best, most modern image t=
o build that should be used by=0A> u-boot?=0A>>=0A>> Thanks in advance=0A>>=
=0A>> Joshua=0A>>=0A>> p.s. I've been trying with kernel.org mainline, xili=
nx git and denx=0A> ELDK xenomai (2.6.24).  U-boot is=0A>> built from lates=
t git source.  DTS file built from XPS 9.1i with=0A> latest service packs, =
and turned=0A>> into DTB with latest dtc source from git.=0A>>=0A>>=0A>> --=
=0A>> Xiphos Technologies=0A>> (514) 847-9474 x227=0A>> (514) 848-9644 fax=
=0A>>=0A>> www.xiphos.com=0A>> ____________________________________________=
___=0A>> The information transmitted is intended only for the=0A>> person o=
r entity to which it is addressed and may contain=0A>> confidential and/or =
privileged material.  If you have=0A>> received this in error, please conta=
ct the sender and delete=0A>> this communication and any copy immediately. =
Thank you.=0A>>=0A>>=0A>>=0A>> ____________________________________________=
___=0A>> Linuxppc-embedded mailing list=0A>> Linuxppc-embedded@ozlabs.org=
=0A>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded=0A> =0A> =0A> T=
his email and any attachments are intended for the sole use of the named=0A=
> recipient(s) and contain(s) confidential information that may be propriet=
ary,=0A> privileged or copyrighted under applicable law. If you are not the=
 intended=0A> recipient, do not read, copy, or forward this email message o=
r any attachments.=0A> Delete this email message and any attachments immedi=
ately.=0A> =0A> =0A> _______________________________________________=0A> Li=
nuxppc-embedded mailing list=0A> Linuxppc-embedded@ozlabs.org=0A> https://o=
zlabs.org/mailman/listinfo/linuxppc-embedded=0A> =0A=0A=0A-- =0AXiphos Tech=
nologies=0A(514) 847-9474 x227=0A(514) 848-9644 fax=0A=0Awww.xiphos.com=0A_=
______________________________________________=0AThe information transmitte=
d is intended only for the=0Aperson or entity to which it is addressed and =
may contain=0Aconfidential and/or privileged material.  If you have=0Arecei=
ved this in error, please contact the sender and delete=0Athis communicatio=
n and any copy immediately. Thank you.=0A=0A=0A

RE: virtex uImage and serial ports

[John Linn]

It's been a while, but here's what I remember.

You have to have SERIAL_OF* turned on in the kernel configuration to get
the code to work.

Then the device tree gets parsed by of_serial.c functions for the 16550
uart.

-- John

> -----Original Message-----
> From: Joshua Lamorie [mailto:jpl@xiphos.ca]
> Sent: Tuesday, December 30, 2008 12:14 PM
> To: John Linn
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: virtex uImage and serial ports
> =

> Gidday John,
> =

> Thanks for the pointer.  I think I have already gone through every
possible page on the wiki, without
> finding my answer.  There are some great pointers however, such as
> http://xilinx.wikidot.com/debugging-kernel-boot-problems.
> =

> As far as I can tell, if I do 'make uImage', there is no code built
into vmlinux that will parse the
> device tree and set up the serial ports (at least as far as I can see
with objdump -S).  When it
> boots, there is no console output and __log_buf doesn't show any
serial ports detected during the
> initialization of the serial driver.
> =

> Which leads to my question, how does the 8250 serial driver get the
information about the attached
> serial ports from the dtb?  Which part of the code parses the dtb,
finds the "ns16550" and
> updates/builds the platform_device information for the 8250 serial
port driver?
> =

> Joshua
> =

> On Tuesday, 30 December, 2008 13:16, "John Linn"
<John.Linn@xilinx.com> said:
> =

> > Hi Joshua,
> >
> > Have you looked at our wiki site at http://xilinx.wikidot.com as we
> > quite a bit of information there.
> >
> > The ML405 board is a V2Pro chip so it should be pretty close to what
you
> > want using the default kernel config for virtex4.
> >
> > I haven't tested the console at 115,200 as I use it at 9600.
Shouldn't
> > be a problem, but may not hurt to stay at 9600 to get it working.
> >
> > There are pages on the wiki about using u-boot with the kernel also
as
> > it sounds like that's what you're doing.
> >
> > Thanks,
> > John
> >
> >
> >> -----Original Message-----
> >> From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org
> > [mailto:linuxppc-embedded-
> >> bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Joshua
Lamorie
> >> Sent: Wednesday, December 24, 2008 3:48 PM
> >> To: linuxppc-embedded@ozlabs.org
> >> Subject: virtex uImage and serial ports
> >>
> >> Gidday there,
> >>
> >> I am trying to get 2.6.27(ish) running on my custom Virtex-II Pro
> > platform (I call it Q5).  I already
> >> have many years of running 2.4.26 and booting from u-boot.
> >>
> >> The problem is getting the console running.  I have a device tree
blob
> > built and loaded into memory,
> >> and by peeking at __log_buf I can see that it is reading this okay
> > (i.e. it is correctly finding my
> >> interrupt controller).  However, by the time it goes to mount the
> > ramdisk as root, it complains that
> >> there is no console.
> >>
> >> I'm fairly certain /chosen has stdout pointing to the correct UART,
> > and the console arguments are
> >> ttyS0,115200.
> >>
> >> In looking through the code however, I cannot figure out how the
> > uImage code actually initializes the
> >> serial-ports for the XILINX_VIRTEX_GENERIC_BOARD.  As I understand
it,
> > the only place where
> >> serial_console_init is called, is within platform_init, and this
isn't
> > called for uImage.
> >>
> >> So, three questions.
> >>
> >> 1) How is the serial driver supposed to know where the platforms
> > serial ports are?
> >>
> >> 2) If I wanted to scrap u-boot and just copy kernel/ramdisk/dtb to
> > memory, which kernel make target
> >> should I use?  dtbImage, simpleImage?
> >>
> >> 3) What is the best, most modern image to build that should be used
by
> > u-boot?
> >>
> >> Thanks in advance
> >>
> >> Joshua
> >>
> >> p.s. I've been trying with kernel.org mainline, xilinx git and denx
> > ELDK xenomai (2.6.24).  U-boot is
> >> built from latest git source.  DTS file built from XPS 9.1i with
> > latest service packs, and turned
> >> into DTB with latest dtc source from git.
> >>
> >>
> >> --
> >> Xiphos Technologies
> >> (514) 847-9474 x227
> >> (514) 848-9644 fax
> >>
> >> www.xiphos.com
> >> _______________________________________________
> >> The information transmitted is intended only for the
> >> person or entity to which it is addressed and may contain
> >> confidential and/or privileged material.  If you have
> >> received this in error, please contact the sender and delete
> >> this communication and any copy immediately. Thank you.
> >>
> >>
> >>
> >> _______________________________________________
> >> Linuxppc-embedded mailing list
> >> Linuxppc-embedded@ozlabs.org
> >> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> >
> > This email and any attachments are intended for the sole use of the
named
> > recipient(s) and contain(s) confidential information that may be
proprietary,
> > privileged or copyrighted under applicable law. If you are not the
intended
> > recipient, do not read, copy, or forward this email message or any
attachments.
> > Delete this email message and any attachments immediately.
> >
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> =

> =

> --
> Xiphos Technologies
> (514) 847-9474 x227
> (514) 848-9644 fax
> =

> www.xiphos.com
> _______________________________________________
> The information transmitted is intended only for the
> person or entity to which it is addressed and may contain
> confidential and/or privileged material.  If you have
> received this in error, please contact the sender and delete
> this communication and any copy immediately. Thank you.
> =

> =

> =

> =



This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.

RE: virtex uImage and serial ports

[Joshua Lamorie]

Gidday John,=0A=0AThanks for the clue.  This works.  Now to get a proper 2.=
6 style (with udev, sysfs and all those new fangled things) root filesystem=
 up and running.  It boots fine with my old 2.4 style buildroot/busybox fil=
esystem.=0A=0AThanks again.=0A=0AJoshua=0A=0AOn Tuesday, 30 December, 2008 =
14:23, "John Linn" <John.Linn@xilinx.com> said:=0A=0A> It's been a while, b=
ut here's what I remember.=0A> =0A> You have to have SERIAL_OF* turned on i=
n the kernel configuration to get=0A> the code to work.=0A> =0A> Then the d=
evice tree gets parsed by of_serial.c functions for the 16550=0A> uart.=0A>=
 =0A> -- John=0A> =0A>> -----Original Message-----=0A>> From: Joshua Lamori=
e [mailto:jpl@xiphos.ca]=0A>> Sent: Tuesday, December 30, 2008 12:14 PM=0A>=
> To: John Linn=0A>> Cc: linuxppc-embedded@ozlabs.org=0A>> Subject: RE: vir=
tex uImage and serial ports=0A>>=0A>> Gidday John,=0A>>=0A>> Thanks for the=
 pointer.  I think I have already gone through every=0A> possible page on t=
he wiki, without=0A>> finding my answer.  There are some great pointers how=
ever, such as=0A>> http://xilinx.wikidot.com/debugging-kernel-boot-problems=
.=0A>>=0A>> As far as I can tell, if I do 'make uImage', there is no code b=
uilt=0A> into vmlinux that will parse the=0A>> device tree and set up the s=
erial ports (at least as far as I can see=0A> with objdump -S).  When it=0A=
>> boots, there is no console output and __log_buf doesn't show any=0A> ser=
ial ports detected during the=0A>> initialization of the serial driver.=0A>=
>=0A>> Which leads to my question, how does the 8250 serial driver get the=
=0A> information about the attached=0A>> serial ports from the dtb?  Which =
part of the code parses the dtb,=0A> finds the "ns16550" and=0A>> updates/b=
uilds the platform_device information for the 8250 serial=0A> port driver?=
=0A>>=0A>> Joshua=0A>>=0A>> On Tuesday, 30 December, 2008 13:16, "John Linn=
"=0A> <John.Linn@xilinx.com> said:=0A>>=0A>> > Hi Joshua,=0A>> >=0A>> > Hav=
e you looked at our wiki site at http://xilinx.wikidot.com as we=0A>> > qui=
te a bit of information there.=0A>> >=0A>> > The ML405 board is a V2Pro chi=
p so it should be pretty close to what=0A> you=0A>> > want using the defaul=
t kernel config for virtex4.=0A>> >=0A>> > I haven't tested the console at =
115,200 as I use it at 9600.=0A> Shouldn't=0A>> > be a problem, but may not=
 hurt to stay at 9600 to get it working.=0A>> >=0A>> > There are pages on t=
he wiki about using u-boot with the kernel also=0A> as=0A>> > it sounds lik=
e that's what you're doing.=0A>> >=0A>> > Thanks,=0A>> > John=0A>> >=0A>> >=
=0A>> >> -----Original Message-----=0A>> >> From: linuxppc-embedded-bounces=
+john.linn=3Dxilinx.com@ozlabs.org=0A>> > [mailto:linuxppc-embedded-=0A>> >=
> bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Joshua=0A> Lamori=
e=0A>> >> Sent: Wednesday, December 24, 2008 3:48 PM=0A>> >> To: linuxppc-e=
mbedded@ozlabs.org=0A>> >> Subject: virtex uImage and serial ports=0A>> >>=
=0A>> >> Gidday there,=0A>> >>=0A>> >> I am trying to get 2.6.27(ish) runni=
ng on my custom Virtex-II Pro=0A>> > platform (I call it Q5).  I already=0A=
>> >> have many years of running 2.4.26 and booting from u-boot.=0A>> >>=0A=
>> >> The problem is getting the console running.  I have a device tree=0A>=
 blob=0A>> > built and loaded into memory,=0A>> >> and by peeking at __log_=
buf I can see that it is reading this okay=0A>> > (i.e. it is correctly fin=
ding my=0A>> >> interrupt controller).  However, by the time it goes to mou=
nt the=0A>> > ramdisk as root, it complains that=0A>> >> there is no consol=
e.=0A>> >>=0A>> >> I'm fairly certain /chosen has stdout pointing to the co=
rrect UART,=0A>> > and the console arguments are=0A>> >> ttyS0,115200.=0A>>=
 >>=0A>> >> In looking through the code however, I cannot figure out how th=
e=0A>> > uImage code actually initializes the=0A>> >> serial-ports for the =
XILINX_VIRTEX_GENERIC_BOARD.  As I understand=0A> it,=0A>> > the only place=
 where=0A>> >> serial_console_init is called, is within platform_init, and =
this=0A> isn't=0A>> > called for uImage.=0A>> >>=0A>> >> So, three question=
s.=0A>> >>=0A>> >> 1) How is the serial driver supposed to know where the p=
latforms=0A>> > serial ports are?=0A>> >>=0A>> >> 2) If I wanted to scrap u=
-boot and just copy kernel/ramdisk/dtb to=0A>> > memory, which kernel make =
target=0A>> >> should I use?  dtbImage, simpleImage?=0A>> >>=0A>> >> 3) Wha=
t is the best, most modern image to build that should be used=0A> by=0A>> >=
 u-boot?=0A>> >>=0A>> >> Thanks in advance=0A>> >>=0A>> >> Joshua=0A>> >>=
=0A>> >> p.s. I've been trying with kernel.org mainline, xilinx git and den=
x=0A>> > ELDK xenomai (2.6.24).  U-boot is=0A>> >> built from latest git so=
urce.  DTS file built from XPS 9.1i with=0A>> > latest service packs, and t=
urned=0A>> >> into DTB with latest dtc source from git.=0A>> >>=0A>> >>=0A>=
> >> --=0A>> >> Xiphos Technologies=0A>> >> (514) 847-9474 x227=0A>> >> (51=
4) 848-9644 fax=0A>> >>=0A>> >> www.xiphos.com=0A>> >> ____________________=
___________________________=0A>> >> The information transmitted is intended=
 only for the=0A>> >> person or entity to which it is addressed and may con=
tain=0A>> >> confidential and/or privileged material.  If you have=0A>> >> =
received this in error, please contact the sender and delete=0A>> >> this c=
ommunication and any copy immediately. Thank you.=0A>> >>=0A>> >>=0A>> >>=
=0A>> >> _______________________________________________=0A>> >> Linuxppc-e=
mbedded mailing list=0A>> >> Linuxppc-embedded@ozlabs.org=0A>> >> https://o=
zlabs.org/mailman/listinfo/linuxppc-embedded=0A>> >=0A>> >=0A>> > This emai=
l and any attachments are intended for the sole use of the=0A> named=0A>> >=
 recipient(s) and contain(s) confidential information that may be=0A> propr=
ietary,=0A>> > privileged or copyrighted under applicable law. If you are n=
ot the=0A> intended=0A>> > recipient, do not read, copy, or forward this em=
ail message or any=0A> attachments.=0A>> > Delete this email message and an=
y attachments immediately.=0A>> >=0A>> >=0A>> > ___________________________=
____________________=0A>> > Linuxppc-embedded mailing list=0A>> > Linuxppc-=
embedded@ozlabs.org=0A>> > https://ozlabs.org/mailman/listinfo/linuxppc-emb=
edded=0A>> >=0A>>=0A>>=0A>> --=0A>> Xiphos Technologies=0A>> (514) 847-9474=
 x227=0A>> (514) 848-9644 fax=0A>>=0A>> www.xiphos.com=0A>> _______________=
________________________________=0A>> The information transmitted is intend=
ed only for the=0A>> person or entity to which it is addressed and may cont=
ain=0A>> confidential and/or privileged material.  If you have=0A>> receive=
d this in error, please contact the sender and delete=0A>> this communicati=
on and any copy immediately. Thank you.=0A>>=0A>>=0A>>=0A>>=0A> =0A> =0A> T=
his email and any attachments are intended for the sole use of the named=0A=
> recipient(s) and contain(s) confidential information that may be propriet=
ary,=0A> privileged or copyrighted under applicable law. If you are not the=
 intended=0A> recipient, do not read, copy, or forward this email message o=
r any attachments.=0A> Delete this email message and any attachments immedi=
ately.=0A> =0A> =0A> _______________________________________________=0A> Li=
nuxppc-embedded mailing list=0A> Linuxppc-embedded@ozlabs.org=0A> https://o=
zlabs.org/mailman/listinfo/linuxppc-embedded=0A> =0A=0A=0A-- =0AXiphos Tech=
nologies=0A(514) 847-9474 x227=0A(514) 848-9644 fax=0A=0Awww.xiphos.com=0A_=
______________________________________________=0AThe information transmitte=
d is intended only for the=0Aperson or entity to which it is addressed and =
may contain=0Aconfidential and/or privileged material.  If you have=0Arecei=
ved this in error, please contact the sender and delete=0Athis communicatio=
n and any copy immediately. Thank you.=0A=0A=0A