From: Avi Kivity <avi@argo.co.il>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ben Duncan <ben@versaccounting.com>, linux-kernel@vger.kernel.org
Subject: Re: Request kernel 2.6.18 ..
Date: Thu, 21 Sep 2006 12:37:49 +0300 [thread overview]
Message-ID: <45125D6D.9080704@argo.co.il> (raw)
In-Reply-To: <1158831256.11109.98.camel@localhost.localdomain>
Alan Cox wrote:
>
> Ar Mer, 2006-09-20 am 19:31 -0500, ysgrifennodd Ben Duncan:
> > Report: 2.6.18 has solved a lot of issues with
> > my 965 chipset Duo Core intel MB and has been
> > extremely stable ...
> >
> > Now, any idea on a timeline for driver for the Marvell IDE
> > controller ?
>
> Possibly never. Marvell don't currently seem to want to play. Now that
> might be for several reasons, one of which is that its someone elses
> chip rebadged. In that case someone has a chance of working out what it
> copies (eg which bits change when you boot with or without a master or
> slave on each channel is a good clue)
>
> The current prognosis however is that you and/or other marvell users are
> going to have to reverse-engineer the thing or just avoid boards using
> that chip.
>
I have such a board, and all-generic-ide appears to work (at least
enough to load the installer from CD, all the rest is SATA). Perhaps it
can be quirked so the parameter won't be necessary?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2006-09-21 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 0:31 Request kernel 2.6.18 Ben Duncan
2006-09-21 0:47 ` Jeff Garzik
2006-09-21 21:36 ` Marvell PATA (was Re: Request kernel 2.6.18 ..) Jeff Garzik
2006-09-21 9:34 ` Request kernel 2.6.18 Alan Cox
2006-09-21 9:37 ` Avi Kivity [this message]
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=45125D6D.9080704@argo.co.il \
--to=avi@argo.co.il \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@versaccounting.com \
--cc=linux-kernel@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.