From: Jeff Harrell <jharrell@ti.com>
To: Conrad Parker <conradp@cse.unsw.edu.au>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: question concerning serial console setup
Date: Sun, 16 Jan 2000 20:41:38 -0700 [thread overview]
Message-ID: <38828F72.F0FA585@ti.com> (raw)
In-Reply-To: 19991230114736.C18261@cse.unsw.edu.au
[-- Attachment #1: Type: text/plain, Size: 3556 bytes --]
Conrad Parker wrote:
> On Wed, Dec 29, 1999 at 12:23:07PM -0700, Jeff Harrell wrote:
> > I wonder if anybody might have some information concerning the setup of
> > a serial console device
> > on the MIPS/Linux platform. I have been looking at the sgi (indy)
> > source code to determine how to
> > setup a serial console device. The file arch/mips/sgi/kernel/setup.c
> > contains a call to "console_setup"
> > passing the parameters "ttys0" and NULL. I have had some trouble
> > locating the routine that this is
> > actually calling (file, directory?). It looks like there is a version
> > in printk.c and in one of the char drivers (serial167.c).
> > These do not seem like the correct routines.
>
> the version in serial167.c is commented out and looks like it was once
> there only as a placeholder.
>
> console_setup() in printk.c is the correct one, but it doesn't do everything
> you want. It simply determines which of the possible consoles is the system
> ("preferred") console. Normally this is called via parse_options in
> init/main.c so you can set it on booting by passing the kernel parameter
> console=blah, but it can be called any time before the kernel calls
> console_init() (which it does immediately after calling parse_options, in
> order to get the console up asap). If you've configured the kernel to run a
> serial console, console_init() (which is in drivers/char/tty_io.c) will call
> serial_console_init().
>
Hmmm....strange I tried to use console_setup in the same way that setup.c
called
it in ../arch/mips/sgi/kernel/setup.c and ran into linker problems. It looks
like
setup_console is defined statically (sp?) in printk.c.
Here is how it is called in setup.c:
#if defined(CONFIG_SERIAL_CONSOLE) || defined(CONFIG_PROM_CONSOLE)
extern void console_setup(char *, int *);
#endif
...
....
#ifdef CONFIG_SERIAL_CONSOLE
/* ARCS console environment variable is set to "g?" for
* graphics console, it is set to "d" for the first serial
* line and "d2" for the second serial line.
*/
ctype = prom_getenv("console");
if(*ctype == 'd') {
if(*(ctype+1)=='2')
console_setup ("ttyS1", NULL);
else
console_setup ("ttyS0", NULL);
}
Here is how it looks in printk.c:
static int __init console_setup(char *str)
{ .....
I guess I am seeing the error that I would expect to see, i.e., the linker
gives me an
undefined reference. Any ideas how this worked in the sgi code?
>
> For the SGI/MIPS, (the code you're looking at in
> arch/mips/sgi/kernel/setup.c) the choice of serial console can be
> determined by querying the prom settings, so rather than forcing this to be
> a boot parameter the correct console is set up at runtime. (If I'm not
> mistaken, this can still be overriden by passing a kernel parameter, as
> this bit of setup is called way before init/main.c calls parse_options()).
> However, you don't need to call console_setup() in your platform setup
> routine -- it's only done here for convenience.
Unfortunately I am working on an embedded platform, only using this code
as a starting point for our design. If possible I would like to initialize the
console w/o the use of command line parameters.
Any insight that you can provide would be greatly appreciated.
Thanks,
Jeff
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell Work: (801) 619-6104
Broadband Access group/TI
jharrell@ti.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: Type: text/html, Size: 4524 bytes --]
next prev parent reply other threads:[~2000-01-17 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-29 19:23 question concerning serial console setup Jeff Harrell
1999-12-30 0:47 ` Conrad Parker
2000-01-17 3:41 ` Jeff Harrell [this message]
2000-01-17 4:06 ` Ralf Baechle
2000-01-18 1:56 ` Andrew R. Baker
2000-01-18 2:14 ` Ralf Baechle
2000-01-18 2:47 ` Andrew R. Baker
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=38828F72.F0FA585@ti.com \
--to=jharrell@ti.com \
--cc=conradp@cse.unsw.edu.au \
--cc=linux@cthulhu.engr.sgi.com \
/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