linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Uwe Koziolek <uwe.koziolek@gmx.net>,
	"linux.ide" <linux-ide@vger.kernel.org>,
	Sven Ladegast <sven@linux4geeks.de>
Subject: Re: [PATCH 2.6.20-rc3-mm1 2/2] libata: SiS 180 pata/sata support
Date: Mon, 8 Jan 2007 12:51:16 +0000	[thread overview]
Message-ID: <20070108125116.015da28f@localhost.localdomain> (raw)
In-Reply-To: <45A22E9F.1050607@garzik.org>

> It is /very/ bad policy to force the user to load a driver that drives 
> real hardware, just to be able to access a few functions.  Hardware and 
> probe side effects are a very real possibility, and with this setup, the 

No they are not.

> user has /less/ control than normal over things such as load order when 
> pata_sis is loaded as a dependency.

Where did I put the 2x4

Right....

* Whack * ;)

The only probing the SiS driver does is for devices matching the SiS PCI
identifiers in question. Since they are intergrated bridges it's actually
physically impossible to obtain a box which contains both at once

* Whack * ;)

If it was added as a library then the non library driver would look
contain only a call to register the pci driver and a PCI table. The other
7.5K would be waste space. That also means there is no load order issue.

* Whack * ;)

Now if this was an ISA driver or poked around in ugly places your
argument would make sense. In this case I don't think your argument makes
sense, but if you want a pointless tiny pata_sis module to waste memory
on everyones boxes you can just ask and I'll send you a diff or two.

Alan

  reply	other threads:[~2007-01-08 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  1:33 [PATCH 2.6.20-rc3-mm1 2/2] libata: SiS 180 pata/sata support Jeff Garzik
2007-01-08 10:28 ` Alan
2007-01-08 11:44   ` Jeff Garzik
2007-01-08 12:51     ` Alan [this message]
2007-01-08 12:50       ` Jeff Garzik
2007-01-08 15:30         ` Alan

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=20070108125116.015da28f@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=sven@linux4geeks.de \
    --cc=uwe.koziolek@gmx.net \
    /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;
as well as URLs for NNTP newsgroup(s).