linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: different device file name when relocating SMC1?
Date: Sat, 24 Jul 2004 09:07:46 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0407240816340.11139@localhost.localdomain> (raw)


      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/

             reply	other threads:[~2004-07-24 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 13:07 Robert P. J. Day [this message]
2004-07-25 16:27 ` different device file name when relocating SMC1? Wolfgang Denk

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=Pine.LNX.4.60.0407240816340.11139@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).