From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Marcin Kuk <marcin.kuk@gmail.com>
Cc: Linux IDE Mailing List <linux-ide@vger.kernel.org>
Subject: Re: toshiba ide - ide dma setting
Date: Tue, 8 Feb 2005 23:04:57 +0100 [thread overview]
Message-ID: <58cb370e050208140441bef38f@mail.gmail.com> (raw)
In-Reply-To: <28d670ae0502081341467eb64f@mail.gmail.com>
On Tue, 8 Feb 2005 22:41:45 +0100, Marcin Kuk <marcin.kuk@gmail.com> wrote:
> > Have you tried "Generic PCI IDE Chipset Support" ?
>
> I thing that you are about:
> generic / default IDE chipset support (kernel 2.6.10) ?
No...
> Probably in 2.4 series the name was as you quoted.
> Yes. This option was compiled in kernel.
>
> All kernels were compiled with setting all chipsets.
> I cared about set all of options responsible for IDE.
> All IDE drivers was compiled into kernel (not modules).
> CONFIG_BLK_DEV_GENERIC=y
...but you have it.
output of lspci command would be also helpful
> I think that the solution of my problem is here:
> http://marc.theaimsgroup.com/?l=linux-ide&m=109967556605057&w=2
> and here is your response:
> http://marc.theaimsgroup.com/?l=linux-ide&m=109969178814722&w=2
>
> "AFAICS this option allows users to use generic code for
> unknown/unsupported devices which can result in unpredictable results
> (hangs, data corruptions)." BZ
This patch is in Alan's -ac tree.
Just get the latest patch for 2.6.10 from:
http://kernel.org/pub/linux/kernel/people/alan/linux-2.6/2.6.10/
next prev parent reply other threads:[~2005-02-08 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 19:39 toshiba ide - ide dma setting Marcin Kuk
2005-02-08 20:44 ` Bartlomiej Zolnierkiewicz
[not found] ` <28d670ae0502081341467eb64f@mail.gmail.com>
2005-02-08 21:57 ` Marcin Kuk
2005-02-08 22:04 ` Bartlomiej Zolnierkiewicz [this message]
2005-02-08 22:32 ` Marcin Kuk
2005-02-09 2:00 ` Marcin Kuk
2005-02-09 22:57 ` Marcin Kuk
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=58cb370e050208140441bef38f@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=marcin.kuk@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).