Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [RFC] Patch to handle parisc-device quirks/bugs.
Date: 17 Nov 2002 13:22:52 -0700	[thread overview]
Message-ID: <1037564572.27005.20.camel@beavis> (raw)
In-Reply-To: <20021117200021.E7530@parcelfarce.linux.theplanet.co.uk>

On Sun, 2002-11-17 at 13:00, Matthew Wilcox wrote:
> On Sun, Nov 17, 2002 at 12:05:09PM -0700, Ryan Bradetich wrote:
> > The following patch fixes this problem by adding a HP hardare
> > quirks table, and fixing up the device early on in the discovery
> > process so everything else just works.
> 
> We have some other occurrences of this kind of problem:
> 
> Graphics cards are frequently wrong.
> HSC-PCI cards show up with the wrong sversion in 715/Mirage machines.
> One of the Dinos in the J2240 has the wrong sversion.

These could easily be added to the quirks list also :)

> We ignore the problem for gfx cards since we don't use the IDs anyway.
> The Dino problems are solved by additional IDs in the Dino driver.

ditto.

> It is legitimate for a driver to refuse to claim a device that it's
> advertised for.  So my personl preference is to advertise for all BC
> ports, and then refuse to claim the ones which are actually lower ports.
> That confines the knowledge to one driver.


So for this case, you would rather see the U2 GSC+ port added to the
hppb.c driver, and simply not-claim any driver that does not reside on
the central bus?  This would work because ccio only claims devices for
the U2 runway side, not the GSC side.

> This scheme doesn't fix the device name printout, but that seems less
> important.

The quirks fixes the print-outs, plus all these problems are fixed in
one place, drivers do not even to know there was a problem.

Either way works for me really, just pointing out the reason I built it
as a quirk table to begin with.

Thanks,

-Ryan

> -- 
> Revolutions do not require corporate support.
> 

  reply	other threads:[~2002-11-17 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 19:05 [parisc-linux] [RFC] Patch to handle parisc-device quirks/bugs Ryan Bradetich
2002-11-17 19:33 ` Grant Grundler
2002-11-17 19:56   ` Ryan Bradetich
2002-11-17 20:00 ` Matthew Wilcox
2002-11-17 20:22   ` Ryan Bradetich [this message]
2002-11-17 20:48     ` Grant Grundler

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=1037564572.27005.20.camel@beavis \
    --to=rbradetich@uswest.net \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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