From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Cc: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
Subject: [parisc-linux] LASI and serial port initialization
Date: Tue, 19 Oct 1999 09:30:45 -0700 [thread overview]
Message-ID: <199910191630.JAA27454@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 18 Oct 1999 21:49:29 PDT." <99101821580101.00297@P100>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2432 bytes --]
Helge and I exchanged some e-mail on the topic of LASI vis a vie
serial port initialization. Since then, I've come to the conclusion
all (or most) parisc platforms will have a similar problem.
The problem is LASI is "discovered" and initialized well after several
other drivers want to print things to the console. I see a few options
on how to handle it:
1) For each platform, force the console to be the first device "discovered"
and initialized. This is not a really good idea since console can be
different depending on configuration. Rebuilding the kernel to use
a different console doesn't seem reasonable to me. Having the user
figure out which devices need to be initialized first and build an
appropriate kernel so console works also seems unreasonable. We are
headed down this path now though....
2) Use IODC until the console device is "owned" by the appropriate driver
and can start taking input/output.
3) buffer the output instead of calling IODC.
Size of the buffer will impose some sort of limit.
I think this is what HP-UX does but don't really know
and it shouldn't matter to us.
Either 2 or 3 requires some software layer behind printk to change
behavior at some point. I don't know where that point is or how
exactly to define it. I just thought going down path #1 is going
to be a real pain to support on a broad set of platforms.
Any other thoughts?
BTW, I still don't know if Helge's changes to inventory.c are
needed or not. I don't have the warm fuzzy feeling they are needed
but can't prove they aren't either.
grant
Helge Deller wrote:
> Am Mon, 18 Oct 1999 schrieben Sie:
> > Helge,
> > I never understood this chunk of very well. I was wondering
> > why you moved code from the case HPHW_BA to outside the switch
> > statement in do_oldhw_inventory()? (inventory.c)
> >
> > If this is of general interest please post to parisc-linux...
> >
> > thanks,
> > grant
>
> Hi Grant.
>
> I just wanted to get it working, so I moved stuff around until it worked. Wit
> h
> this I found, that the LASI-Controller should be added to the list before all
> other stuff underlying the lasi (same is also to the WAX(??)-controller with
> PS2/Keyboard/Mouse/RS232/HIL). This way it worked and I didn´t thought too muc
> h
> about it later.... :-)
>
> [Is this for global interrest ??]
Grant Grundler
Communications Infrastructure Computer Operations
+1.408.447.7253
next parent reply other threads:[~1999-10-19 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99101821580101.00297@P100>
1999-10-19 16:30 ` Grant Grundler [this message]
1999-10-19 16:46 ` [parisc-linux] LASI and serial port initialization Frank Rowand
1999-10-19 16:58 ` Alan Cox
1999-10-19 17:22 ` Philipp Rumpf
1999-10-19 17:32 Mike Hibler
1999-10-19 18:36 ` Grant Grundler
1999-10-19 20:13 ` Phil Schwan
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=199910191630.JAA27454@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=Helge.Deller@ruhr-uni-bochum.de \
--cc=parisc-linux@thepuffingroup.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