From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>,
linux-main <linux-kernel@vger.kernel.org>
Subject: Re: Best way to detect CF id strings
Date: Tue, 4 Dec 2007 21:37:53 +0100 [thread overview]
Message-ID: <20071204213753.5e376d03.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <20071204203038.20e7ca55@the-village.bc.nu>
On Tue, 4 Dec 2007 20:30:38 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Tue, 4 Dec 2007 20:19:33 +0100
> Kristoffer Ericson <kristoffer.ericson@gmail.com> wrote:
>
> > Greetings,
> >
> > Usually I detect them by attaching CF->PCMCIA adapter to my laptop, but would much rather be able to use my usb-CF adapter.
> > This would also alot easier to explain to users which are having issues (unsupported/unknown id's).
>
> What sort of "id" are we talking about here ?
Manufacturer and product id. Since the CF needs to be known to be used as an ide-cs device.
prev parent reply other threads:[~2007-12-04 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 19:19 Best way to detect CF id strings Kristoffer Ericson
2007-12-04 20:30 ` Alan Cox
2007-12-04 20:37 ` Kristoffer Ericson [this message]
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=20071204213753.5e376d03.Kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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