From: Andrey Panin <pazke@donpac.ru>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Jacques Goldberg <Jacques.Goldberg@cern.ch>
Subject: Re: Need break driver<-->pci-device automatic association
Date: Mon, 21 Mar 2005 11:16:38 +0300 [thread overview]
Message-ID: <20050321081638.GC2703@pazke> (raw)
In-Reply-To: <Pine.LNX.4.58_heb2.09.0503192021431.11358@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On 078, 03 19, 2005 at 08:33:14PM +0200, Jacques Goldberg wrote:
>
> Good news!
> That's really what is needed (mainline).
> I attach the file which Sasha, author or the lmodem driver, has
> modified and then it works for the chips hard-wired in the routine.
> To locate the patched area, look for 5457
We can use PCI quirk here. Patch attached.
> I am an experimental physicist, not a computer expert. If this kind of
> algorithm could be implemented in the mainlin 8250_pci.c , then I would
> dream of looking for an /etc/config file containing such a list, whose
> objects would be skipped by the serial driver.
> Sorry to repeat myself, but avoiding the need for the users to
> recompile a kernel should be the first worry when implementing a solution.
It's not a reason to fill kernel code with ugly kludges :)
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: patch-quirk-winmodems --]
[-- Type: text/plain, Size: 1048 bytes --]
diff -urdpNX /usr/share/dontdiff linux-2.6.11.vanilla/drivers/pci/quirks.c linux-2.6.11/drivers/pci/quirks.c
--- linux-2.6.11.vanilla/drivers/pci/quirks.c 2005-03-02 10:37:31.000000000 +0300
+++ linux-2.6.11/drivers/pci/quirks.c 2005-03-21 11:02:53.000000000 +0300
@@ -1241,6 +1241,18 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_IN
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_E7320_MCH, quirk_pcie_mch );
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_E7525_MCH, quirk_pcie_mch );
+/*
+ * Some stupid winmodems try to look as real modems. Fix them.
+ */
+static void __devinit quirk_winmodems(struct pci_dev *dev)
+{
+ dev->class = PCI_CLASS_COMMUNICATION_OTHER;
+}
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AL, PCI_DEVICE_ID_AL_M5451, quirk_winmodems);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AL, 0x5457, quirk_winmodems);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AL, 0x5459, quirk_winmodems);
+
+
static void pci_do_fixups(struct pci_dev *dev, struct pci_fixup *f, struct pci_fixup *end)
{
while (f < end) {
next prev parent reply other threads:[~2005-03-21 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 8:57 Need break driver<-->pci-device automatic association Jacques Goldberg
2005-03-18 13:14 ` Alan Cox
2005-03-18 13:58 ` Jacques Goldberg
2005-03-18 14:39 ` Stuart MacDonald
2005-03-19 18:18 ` Jacques Goldberg
2005-03-18 16:51 ` Greg KH
2005-03-19 18:33 ` Jacques Goldberg
2005-03-21 8:16 ` Andrey Panin [this message]
2005-03-21 8:22 ` Russell King
2005-03-21 8:40 ` Andrey Panin
2005-03-21 11:39 ` Jacques Goldberg
2005-03-21 20:18 ` Russell King
2005-03-21 20:57 ` Jacques Goldberg
2005-03-21 21:09 ` Russell King
2005-03-21 21:30 ` Jacques Goldberg
2005-03-21 11:35 ` Jacques Goldberg
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=20050321081638.GC2703@pazke \
--to=pazke@donpac.ru \
--cc=Jacques.Goldberg@cern.ch \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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