From: Robert de Rooy <robert.de.rooy@gmail.com>
To: albertl@mail.com
Cc: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
bzolnier@gmail.com, linux-pcmcia@lists.infradead.org,
Kernel development list <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Mark Lord <liml@rtr.ca>, Alan <alan@lxorguk.ukuu.org.uk>
Subject: [Fwd: Re: libata and legacy ide pcmcia failure]
Date: Mon, 25 Jun 2007 21:11:30 +0200 [thread overview]
Message-ID: <46801362.3040605@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 52 bytes --]
Oops had done a reply instead of a reply to all...
[-- Attachment #2: Re: libata and legacy ide pcmcia failure.eml --]
[-- Type: message/rfc822, Size: 2264 bytes --]
From: Robert de Rooy <robert.de.rooy@gmail.com>
To: albertl@mail.com
Subject: Re: libata and legacy ide pcmcia failure
Date: Mon, 25 Jun 2007 13:38:35 +0200
Message-ID: <467FA93B.6010403@gmail.com>
Albert Lee wrote:
> The patch just workarounds the "lost irq" problem by polling; not real
> fix. We still need to find out why irq is lost per Mark's comment:
>
> "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."
>
> "So, next step might be to try and understand the interrupt mis-delivery
> problem some more. I've lost the history of the original issue,
> but we now know that everything except the actual interrupt seems good."
>
> I am not familiar with the PCMCIA interrupt delivery. It seems the
> "Dazzle 4in1 Card Adapter" works under windows but somehow lost irq
> under both IDE and libata. Maybe Alan/Bart or the PCMCIA developers
> know better...
> --
> albert
I see. So this is not the ideal fix for this problem. Anything else I
can do to debug the irq lost issue? perhaps add some debug to the pcmcia
code?
For what its worth, I compiled a clean 2.6.22-rc5 with just the
pio_polling patch added, and that allows me to mount the device without
any errors in syslog. So the
disable-dev_init_param-and-setxfermode-for-CFA.patch is not needed.
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2007-06-25 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46801362.3040605@gmail.com \
--to=robert.de.rooy@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bzolnier@gmail.com \
--cc=htejun@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 \
/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).