From: Soeren Sonnenburg <kernel@nn7.de>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: szepe@pinerecords.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: re: Linux 2.4.21pre4-ac5 status report
Date: 01 Mar 2003 14:04:18 +0100 [thread overview]
Message-ID: <1046523858.26074.7.camel@sun> (raw)
In-Reply-To: <200303011252.h21CqBpl013357@harpo.it.uu.se>
On Sat, 2003-03-01 at 13:52, Mikael Pettersson wrote:
> On 01 Mar 2003 11:47:39 +0100, Soeren Sonnenburg wrote:
> >> I've got a single pdc20268 with just one drive on each channel...
> >> Works nicely with recent -ac kernels.
> >
> >As I guessed. I've got two pdc20268 with just one drive per channel
> >(where the last drive is a cdrom-drive)
> >
> >So one pdc no problem >1 -> trouble.
>
> It might not have anything to do with your problem, but it has
> been reported several times that Promise chips don't support ATAPI
> optical devices (i.e. your CD-ROM) without special driver support,
> which the Linux drivers apparently don't have.
Yes it doesn't have to do with my particular problem as I tried without
an ATAPI cdrom attached.
> Maybe that's changed in 2.4.21-pre-ac new IDE code, I don't know.
>
> Your cards don't share interrupts with anything else I hope?
sure they do. however it did not work when the pdc's did not share an
IRQ with any other device.
however the htp370 works fine with shared irqs and atapi cdrom.
Soeren.
next prev parent reply other threads:[~2003-03-01 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 12:52 Linux 2.4.21pre4-ac5 status report Mikael Pettersson
2003-03-01 13:04 ` Soeren Sonnenburg [this message]
2003-03-03 19:51 ` Edward King
2003-03-03 19:57 ` Tomas Szepe
2003-03-03 20:56 ` Soeren Sonnenburg
-- strict thread matches above, loose matches on Subject: below --
2003-03-01 8:14 Soeren Sonnenburg
2003-03-01 8:57 ` Tomas Szepe
2003-03-01 10:29 ` Soeren Sonnenburg
2003-03-01 10:32 ` Tomas Szepe
2003-03-01 10:47 ` Soeren Sonnenburg
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=1046523858.26074.7.camel@sun \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
--cc=szepe@pinerecords.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