From: Robert de Rooy <robert.de.rooy@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <htejun@gmail.com>,
linux-kernel@vger.kernel.org, Alan <alan@lxorguk.ukuu.org.uk>,
bzolnier@gmail.com, linux-pcmcia@lists.infradead.org
Subject: Re: libata and legacy ide pcmcia failure
Date: Tue, 22 May 2007 21:37:29 +0200 [thread overview]
Message-ID: <46534679.4030505@gmail.com> (raw)
In-Reply-To: <46520B36.90409@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> Robert de Rooy wrote:
>>> Hmm, good question. I do not have any other PCMCIA device to test.
>>> The only other device I have is a Cardbus Wi-Fi adapter without Linux
>>> support (Marvell). If I insert that adapter lspci seems to list it
>>> properly, but without resorting to ndiswrapper I have no way of testing
>>> it. In any case, seeing how Cardbus is PCI based this is probably
>>> pointless to resolving this issue.
>>>
>>> Would any other log data from the controller initialization or lspci
>>> help?
>>
>> Hmmm... I don't really know much about PCMCIA. cc'ing linux-pcmcia.
>>
>> The original thread can be read from the following URL.
>>
>> http://thread.gmane.org/gmane.linux.kernel/530099
>>
>> It seems we're losing interrupts from the CFA device. Any ideas?
>
> Alan probably knows more, but ISTR some CFA PCMCIA devices that needed
> polling...
>
> This isn't an ARM platform perchance, is it?
>
> Jeff
>
>
>
No, it is a ThinkPad T41 with Intel Pentium M.
I have posted full logs to the list, but the copy to linux-pcmcia got
stuck in moderator approval due to exceeding a 40KB limit.
next prev parent reply other threads:[~2007-05-22 19:37 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 [this message]
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
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=46534679.4030505@gmail.com \
--to=robert.de.rooy@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).