public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: "Joshua Lamorie" <jpl@xiphos.ca>
To: linuxppc-embedded@ozlabs.org
Subject: virtex uImage and serial ports
Date: Wed, 24 Dec 2008 17:48:01 -0500 (EST)	[thread overview]
Message-ID: <1230158881.82162837@192.168.1.35> (raw)

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

             reply	other threads:[~2008-12-24 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24 22:48 Joshua Lamorie [this message]
2008-12-30 18:16 ` virtex uImage and serial ports John Linn
2008-12-30 19:13   ` Joshua Lamorie
2008-12-30 19:23     ` John Linn
2008-12-30 21:18       ` Joshua Lamorie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1230158881.82162837@192.168.1.35 \
    --to=jpl@xiphos.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox