From: "Michael S. Zick" <mszick@wolfbutter.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] NCR_700 problems on 715/64 with 2.6.11-rc4-pa1
Date: Sat, 19 Feb 2005 09:20:23 -0600 [thread overview]
Message-ID: <200502190920.23475.mszick@wolfbutter.com> (raw)
In-Reply-To: <200502191559.26297.deller@gmx.de>
On Sat February 19 2005 08:59, Helge Deller wrote:
> Hi Michael,
>
> On Saturday 19 February 2005 15:00, Michael S. Zick wrote:
> > On Sat February 19 2005 05:34, Helge Deller wrote:
> > > I get random messages from the 53c700 scsi driver (see below).
> > > Any ideas ?
> > > Helge
> > >
> > Looks like more udev/irq balance/irq routing problems,
> > see concurrent thread "BUG 2.6.11-rc4..."
> >
> > try: 'noudev pci=routeirq' options on the command line
> > to change behavior in generic code.
>
> I will try, but I'm not sure that this is the cause.
> Looks to me more like a missing ioremap() call.
>
> Even the sti framebuffer does not work since weeks - I think it's due to ioremap() as well.
>
With 2.6.11 the device drivers are responsible for registering
their irq handling, not the bus driver...
Could that also be the cause for your missing ioremap() calls?
The above is a general description - perhaps not exact.
I am afraid I will learn more than I ever wanted to know about
this change before I get this *&%^& tulip driver working under 2.6.11
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-02-19 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 11:34 [parisc-linux] NCR_700 problems on 715/64 with 2.6.11-rc4-pa1 Helge Deller
2005-02-19 14:00 ` Michael S. Zick
2005-02-19 14:59 ` Helge Deller
2005-02-19 15:20 ` Michael S. Zick [this message]
2005-02-19 16:40 ` Matthew Wilcox
2005-02-19 16:53 ` Matthew Wilcox
2005-02-19 22:12 ` Joel Soete
2005-02-20 12:32 ` Helge Deller
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=200502190920.23475.mszick@wolfbutter.com \
--to=mszick@wolfbutter.com \
--cc=parisc-linux@lists.parisc-linux.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