linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <mlord@pobox.com>
Cc: Robert de Rooy <robert.de.rooy@gmail.com>,
	Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
	bzolnier@gmail.com, linux-pcmcia@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: libata and legacy ide pcmcia failure
Date: Tue, 12 Jun 2007 12:24:15 +0900	[thread overview]
Message-ID: <466E11DF.5020901@gmail.com> (raw)
In-Reply-To: <466DCF43.5060304@pobox.com>

Mark Lord wrote:
> Robert de Rooy wrote:
>> (after applying the ide-polling experimental patch)
>>
>> With this I can declare success!! I was able to read and write to the
>> card without any problems, although I did not try to stress it.
>>
>> Jun 12 00:19:42 localhost kernel: pccard: PCMCIA card inserted into
>> slot 0
>> Jun 12 00:19:42 localhost kernel: cs: memory probe
>> 0xe8000000-0xefffffff: excluding 0xe8000000-0xefffffff
>> Jun 12 00:19:42 localhost kernel: cs: memory probe
>> 0xc0200000-0xcfffffff: excluding 0xc0200000-0xc11fffff
>> 0xc1a00000-0xc21fffff 0xc2a00000-0xc31fffff 0xc3a00000-0xcc1fffff
>> 0xcca00000-0xcd1fffff 0xcda00000-0xce1fffff 0xcea00000-0xcf1fffff
>> 0xcfa00000-0xd01fffff
>> Jun 12 00:19:42 localhost kernel: pcmcia: registering new device
>> pcmcia0.0
>> Jun 12 00:19:42 localhost kernel: Uniform Multi-Platform E-IDE driver
>> Revision: 7.00alpha2
>> Jun 12 00:19:42 localhost kernel: ide: Assuming 33MHz system bus speed
>> for PIO modes; override with idebus=xx
>> Jun 12 00:19:45 localhost kernel: hda: Memory Card Adapter, CFA DISK
>> drive
>> Jun 12 00:19:45 localhost kernel: ide0 at 0x4100-0x4107,0x410e on irq 3
>> Jun 12 00:19:45 localhost kernel: ide-cs: hda: Vpp = 0.0
>> Jun 12 00:19:45 localhost udevd-event[20730]: udev_rules_apply_format:
>> unknown format variable '$modalias'
>> Jun 12 00:19:45 localhost kernel: hda: max request size: 128KiB
>> Jun 12 00:19:45 localhost kernel: hda: 253696 sectors (129 MB) w/1KiB
>> Cache, CHS=991/16/16
>> Jun 12 00:19:45 localhost kernel:  hda: hda1
>> Jun 12 00:19:48 localhost hald: mounted /dev/hda1 on behalf of uid 0
> 
> Okay, Tejun / Bart / Alan:
> 
> This proves that the device does work correctly in most respects
> except for interrupt delivery.  The status bits are working and
> it can be probed for, configured, and used.

libata can do most of this too by using ATA_FLAG_PIO_POLLING (doesn't
cover nodata commands tho).

-- 
tejun

  reply	other threads:[~2007-06-12  3:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 18:59 libata pcmcia failure Robert de Rooy
2007-05-17  8:42 ` Robert de Rooy
2007-05-17 20:15   ` libata and legacy ide " Robert de Rooy
2007-05-20 11:31     ` Tejun Heo
2007-05-20 21:13       ` Robert de Rooy
2007-05-21 11:50         ` Tejun Heo
2007-05-21 12:37           ` Alan Cox
2007-05-21 12:42             ` Tejun Heo
2007-05-21 15:10           ` Robert de Rooy
2007-05-21 15:18             ` Tejun Heo
2007-05-21 16:11               ` Robert de Rooy
2007-05-21 16:22                 ` Tejun Heo
2007-05-21 17:16                   ` Robert de Rooy
2007-05-21 21:12                   ` Jeff Garzik
2007-05-22 19:37                     ` Robert de Rooy
2007-05-23 14:02                     ` Alan Cox
2007-05-23 18:47                       ` Robert de Rooy
2007-06-06 20:27                       ` Robert de Rooy
2007-06-07  7:28                         ` Tejun Heo
2007-06-07 19:22                           ` Robert de Rooy
2007-06-08  7:10                             ` Tejun Heo
2007-06-08 12:46                               ` Mark Lord
2007-06-08 22:06                                 ` Robert de Rooy
2007-06-08 22:11                                   ` Mark Lord
2007-06-10  1:01                                     ` Robert de Rooy
2007-06-10 20:46                                       ` Mark Lord
     [not found]                                         ` <466C723C.6000300@gmail.com>
     [not found]                                           ` <20070610221322.GA18196@flint.arm.linux.org.uk>
     [not found]                                             ` <466C7A9F.1080700@rtr.ca>
2007-06-11 22:36                                               ` Robert de Rooy
2007-06-11 22:40                                                 ` Mark Lord
2007-06-12  3:24                                                   ` Tejun Heo [this message]
2007-06-13  1:36                                                     ` Albert Lee
2007-06-14  9:39                                                       ` Tejun Heo
2007-06-22 11:51                                                         ` Robert de Rooy
2007-06-22 13:32                                                           ` Mark Lord
2007-06-25  4:04                                                             ` Albert Lee
2007-06-25  9:31                                                               ` Robert de Rooy
2007-06-25 10:15                                                                 ` Albert Lee

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=466E11DF.5020901@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=mlord@pobox.com \
    --cc=robert.de.rooy@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).