From: Grant Grundler <grundler@parisc-linux.org>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [patch] Get superio serial to work with 2.6
Date: Sun, 7 Dec 2003 11:15:21 -0700 [thread overview]
Message-ID: <20031207181521.GA14466@colo.lackof.org> (raw)
In-Reply-To: <20031207084431.GP20133@tausq.org>
On Sun, Dec 07, 2003 at 12:44:31AM -0800, Randolph Chung wrote:
> > My preference right now is to move those PDC calls into sba_cdio.c.
>
> hmmm.. that looks like a hpux name ;-) sba_iommu.c?
yeah...brainfart. I was up too late last night again...
> > Then add hueristics that call PDC_IO_RESET_AND_CLEAR if suckyio/USB
> > is active or the LAN active. If suckyio serial console, then add code
> > to save/restore suckyio config space around the reset.
> >
> > So quite a bit of hackery that's really only needed when the
> > IO MMU is actually used.
>
> ok, so should i just keep this patch in my private tree for now? or
> commit it and let you fix the rest of it? ;-)
commit and I'll fix the rest later.
> > hrm...I don't have the serial console setup at the moment.
> > I suggest plugging in a USB mouse and moving the mouse around
> > during boot. Not sure that's sufficient but maybe.
>
> i doubt that will make a difference. if the usb driver is not yet loaded
> (i.e. during inventory) i don't thing any usb events will be happening,
> right? anyway, i guess i can try this tomorrow.
It does make a difference. The IODC left HW in an enabled and operational
state when it handed off to the OS. That's harmless for a serial console.
It's not harmless when the device can master DMA transactions and we
reprogram the IO MMU.
grant
prev parent reply other threads:[~2003-12-07 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 4:10 [parisc-linux] [patch] Get superio serial to work with 2.6 Randolph Chung
2003-12-07 8:20 ` Grant Grundler
2003-12-07 8:44 ` Randolph Chung
2003-12-07 18:15 ` Grant Grundler [this message]
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=20031207181521.GA14466@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.