Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Tom Denchfield <td_denchfield@yahoo.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: CF Card Adapter White List Candidate
Date: Wed, 5 Jan 2011 10:18:55 -0800 (PST)	[thread overview]
Message-ID: <369064.19710.qm@web112003.mail.gq1.yahoo.com> (raw)

Hello,

Tejun, this CF card adapter plugs directly into an IDE socket (Channel 0, in my case) on a desktop computer motherboard.  You can see a picture of the adapter in the following URL01:

URL01: http://preview.tinyurl.com/233u92u

I have to power the adapter with a floppy drive power plug because my motherboard's IDE sockets were intentionally manufactured without the pin that could have supplied power through an IDE cable.

Does anyone have a top of the head opinion as to whether there are inherent usage limitations in either this passive CF card adapter and/or in the Linux kernel used with Ubuntu v10.10 that would prevent users with CF cards faster than UDMA/66 (see URL02 below) from being configured by Linux to work at speeds above UDMA/66?  The reason that I ask this question is that I bought both my UDMA/66 CF card and the adapter from the URL01 seller.  It is foreseeable that a lot of customers might have purchased faster CF cards envisioning that they would work at speeds higher than UDMA/66 with the adapter.  The 'Technical Details' section of URL01 does not state anything about UDMA speed usage limitations. 

URL02: http://www.hjreggel.net/cardspeed/index.html

I think that there are CF card adapters on eBay that are similar to the one pictured in URL01 above, and there are also IDE adapters that will hold two CF cards.

Tom

--- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com> wrote:

> From: Tejun Heo <htejun@gmail.com>
> Subject: Re: CF Card Adapter White List Candidate
> To: "Robert Hancock" <hancockrwd@gmail.com>
> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>, linux-ide@vger.kernel.org
> Date: Wednesday, January 5, 2011, 5:51 AM
> Hello,
> 
> On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert Hancock
> wrote:
> > On 01/04/2011 04:18 PM, Tom Denchfield wrote:
> >> As you further recommended, in an attempt to get
> the SD-CF-IDE-DI
> >> IDE to CF Adapter that holds my CF card white
> listed, I am
> >> submitting the attached
> >>
> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
> >> file that has the output from executing four
> terminal commands to
> >> hopefully supply enough information to get it
> whitelisted.
> 
> Thanks.
> 
> >> Although I expect that my RV280 Radeon 9200 Pro
> video card is too
> >> old to expend much effort on, it would be nice to
> also get it
> >> whitelisted so that future newbie Linux users who
> do not know about
> >> using the radeon.modeset=0 parameter on the kernel
> command line
> >> will not be looking at a black screen with a
> blinking cursor when
> >> they attempt to use a LiveCD for troubleshooting,
> or whatever.
> >>
> >> I purposely did not include the URL of one of the
> Internet sites
> >> that sells the adapter in this email in case this
> is a no no.
> 
> I don't think that's a no no unless the intention is
> commercial.
> 
> >> Tejun, I am not sure that I will have either the
> time or the
> >> interest to learn the intricacies of editing
> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
> to add
> >> libata.force=80c to this site in lieu of
> force_cbl=80: so that
> >> fewer people will be asking you questions.  I
> have a ThinkPad
> >> without a HDD plus a laptop adapter that will hold
> my CF card, but
> >> my Think Pad is a lot older than the ones
> discussed on
> >> Compact_Flash_boot_drive.  In addition, I did
> not see any recent
> >> updates to this Internet page, but maybe I can
> find someone to
> >> email who will update this page.
> 
> Yeah, just ping someone.
> 
> > Is there actually any way to identify the adapter
> automatically?
> > AFAIK, these CF-IDE adapters are just passive
> circuitry and there's
> > no way to identify them through software.
> 
> Hmmm... I was thinking this was somehing integrated to the
> machine (so
> the dmidecode), in which case we can combine dmi + pci
> function # +
> port # to whitelist the device, which we already do for
> some type of
> quirks.  If it's a plug in device, we obviously can't
> identify it.
> Tom, is the CF slot integrated to the machine or is it
> something you
> put into the PCMCIA slot?
> 
> Thanks.
> 
> -- 
> tejun
>


      

             reply	other threads:[~2011-01-05 18:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:18 Tom Denchfield [this message]
2011-01-05 23:47 ` CF Card Adapter White List Candidate Robert Hancock
2011-01-06  3:23   ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2011-01-07 16:51 Tom Denchfield
2011-01-08 15:30 ` Robert Hancock
2011-01-06  5:33 Tom Denchfield
2011-01-07  4:22 ` Robert Hancock
2011-01-08 10:48   ` Michael Tokarev
2011-01-08 22:18     ` Tom Denchfield
2011-01-04 22:18 Tom Denchfield
2011-01-05  4:19 ` Robert Hancock
2011-01-05 11:51   ` Tejun Heo

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=369064.19710.qm@web112003.mail.gq1.yahoo.com \
    --to=td_denchfield@yahoo.com \
    --cc=hancockrwd@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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