From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Greg KH <gregkh@suse.de>,
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 08:22:28 +0000 [thread overview]
Message-ID: <20050321082228.A22099@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050321081638.GC2703@pazke>; from pazke@donpac.ru on Mon, Mar 21, 2005 at 11:16:38AM +0300
On Mon, Mar 21, 2005 at 11:16:38AM +0300, Andrey Panin wrote:
> On 078, 03 19, 2005 at 08:33:14PM +0200, Jacques Goldberg wrote:
> > 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 haven't seen any mail in this thread which provides the complete
PCI ID information for these cards. Can someone oblige please, with:
lspci -vv
for the relevant card.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-03-21 8:22 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
2005-03-21 8:22 ` Russell King [this message]
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=20050321082228.A22099@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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