linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* different device file name when relocating SMC1?
@ 2004-07-24 13:07 Robert P. J. Day
  2004-07-25 16:27 ` Wolfgang Denk
  0 siblings, 1 reply; 2+ messages in thread
From: Robert P. J. Day @ 2004-07-24 13:07 UTC (permalink / raw)
  To: Embedded Linux PPC list


      working with the latest 2.4.25 kernel tree from denx (sorry, i know
everyone else is keen on 2.6, but we do have a project to maintain), i
have a baseline kernel config for our 850DE board with SMC1 UART, and
no networking configured in yet.  i just wanted to test the simple
relocation of SMC1 *in* *preparation* for adding ethernet on SCC3, so
i added the ucode patches to shift SMC1 (that was the only change in
the kernel config), and a couple of us moved over the patches from the
old uart.c file as best we could.

      with just this change, all we now get at boot time is:

Linux/PPC load: console=ttyS0,9600 rw root=/dev/ram0
Uncompressing Linux...done.
Now booting the kernel

... and hang ...

      so, simple question -- until now, we've identified the console as
ttyS0, and it's worked fine.  does relocation require referring to the
console with a different device file name?  i (vaguely) recall /dev
entries with names like cpmuart0 or something like that.  given
relocation, should i be using something other than "ttyS0"?

      (chances are, of course, we have to mess with uart.c a bit longer to
see what's different between the two 2.4 kernel trees, but i thought
i'd ask if it could be something this simple.)

rday

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-07-25 16:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-24 13:07 different device file name when relocating SMC1? Robert P. J. Day
2004-07-25 16:27 ` Wolfgang Denk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).