All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: David Brownell <david-b@pacbell.net>
Cc: DaVinci <davinci-linux-open-source@linux.davincidsp.com>,
	linux-ide@vger.kernel.org
Subject: Re: [patch 2.6.29-davinci1 git] dm6446evm CF support
Date: Wed, 01 Apr 2009 22:12:25 +0400	[thread overview]
Message-ID: <49D3AE89.1080500@ru.mvista.com> (raw)
In-Reply-To: <200904011009.10608.david-b@pacbell.net>

Hello.

David Brownell wrote:

>>>+config MACH_DAVINCI_EVM_CF
>>>+     bool "Use CompactFlash, not IDE drive"
>>>+     depends on MACH_DAVINCI_EVM && BLK_DEV_PALMCHIP_BK3710
>>>+     help
>>>+       Enable this if you want to use a CompactFlash card instead of
>>>+       an IDE/ATA drive.  The CF card will be used in "True IDE" mode.
>>>+
>>>+       At this writing, CF insert and remove events are not supported.
>>>+       Insert the CF at boot time, and leave it there until you power
>>>+       the system off.
>>>+

>>    This instruction is already obsolete. As I've already noted, IDE core now 
>>supports warm plug via sysfs, see Documentation/ide/warm-plug-howto.txt. One 
>>can plug and unplug any time, this just won't be automatically noticed by the 
>>kernel, so one will need to notify it.

> CF insert and remove events are very different from writing
> some sysfs files.  They are handled through a pcmcia_socket
> abstraction ... and are completely hands-off.  Socket events
> include card insert/removal detection, and socket operations
> include power on/off and reset.  I don't know that "true-IDE"
> links work through those sockets, though.

> That said ... I tried that manual workaround; it didn't work.

> So:  no, that instruction is far from obsolete.

    So, it would only work with real hard disks... sigh. Sorry for 
disinformation then -- I hoped warm plug could've been helpful for CF.

MBR, Sergei

           reply	other threads:[~2009-04-01 18:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200904011009.10608.david-b@pacbell.net>]

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=49D3AE89.1080500@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=david-b@pacbell.net \
    --cc=davinci-linux-open-source@linux.davincidsp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.