Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Norman Diamond" <n0diamond@yahoo.co.jp>
To: Mark Lord <liml@rtr.ca>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	linux-ide@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel bug crashing in HDIO_DRIVE_TASKFILE
Date: Thu, 26 Feb 2009 20:56:38 +0900	[thread overview]
Message-ID: <B2BE4BF16058416F88555755CB1823DF@DIAMOND8600> (raw)
In-Reply-To: 49A5C9A5.20005@rtr.ca

Mark Lord wrote:
> Norman Diamond wrote:
>>
>> Meanwhile I also can't help wondering, if Mark Lord has patched
>> drivers/ide to make it work, why has he delayed submitting the patches?
>
> There's simply too much churn in drivers/ide for me to keep up with, and
> my patches won't apply to kernels from the past year.

OK!  For my present needs, a year-old kernel didn't need your patches.

This problem with 2.6.27.7 and 2.6.27.8 was solved by grading to 2.6.24.3.
Slax 6.0.3 came with configuration files for 2.6.24.3, I edited the
configuration to set CONFIG_IDE_TASK_IOCTL=y, and the result ran without
crashing -- today anyway.  It still needs more testing.

This kind of solution, fixing a problem by upgrading to an older version, is
something that we normally expect to pay for.  Usually we have to pay for
that kind of software every time we buy a PC.  I'm well aware that this one
came from volunteers, and I ought to contribute by finding where the bug was
introduced, but sorry, I don't have that kind of free time.

> Drivers/ide is on the way out FAST now, and any new systems that still use
> it are mostly based on older kernels, where patches like mine are
> inappropriate for maintenance point releases.

Some are old systems that need their own maintenance, their maintenance
ought to be accompanied by upgrading to newer kernels, and patches would be
very highly appropriate for maintenance point releases.

> Libata should be used for any new setup that doesn't have a strict legacy
> requirement now.

90% agreed.  However, I've read that libata will never support add-on IDE
boards. 

--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/

  reply	other threads:[~2009-02-26 11:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 11:36 Kernel bug crashing in HDIO_DRIVE_TASKFILE Norman Diamond
2009-02-24 22:10 ` Chuck Ebbert
2009-02-25 11:43   ` Norman Diamond
2009-02-25 16:24     ` Mark Lord
2009-02-25 19:35       ` Bartlomiej Zolnierkiewicz
2009-02-25 21:18         ` Norman Diamond
2009-02-25 22:43           ` Mark Lord
2009-02-26 11:56             ` Norman Diamond [this message]
2009-02-28  3:14               ` Robert Hancock
2009-03-01  0:58                 ` Norman Diamond
2009-03-01  1:16                   ` Alan Cox
2009-03-01 11:06                   ` Robert Hancock
2009-03-02  0:24                     ` Norman Diamond
2009-03-02  2:38                       ` Robert Hancock
2009-03-02 11:43                         ` Norman Diamond
2009-03-11 22:33                       ` Bartlomiej Zolnierkiewicz
2009-03-11 23:00                         ` Norman Diamond
  -- strict thread matches above, loose matches on Subject: below --
2009-03-03 11:44 Norman Diamond

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=B2BE4BF16058416F88555755CB1823DF@DIAMOND8600 \
    --to=n0diamond@yahoo.co.jp \
    --cc=bzolnier@gmail.com \
    --cc=cebbert@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox