linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Eric Mudama <edmudama@gmail.com>,
	Greg Freemyer <greg.freemyer@gmail.com>,
	Albert Lee <albertcc@tw.ibm.com>,
	IDE Linux <linux-ide@vger.kernel.org>,
	Doug Maxey <dwm@maxeymade.com>, dan mares <dmares@dmares.com>
Subject: Re: libata PATA support - work items?
Date: Tue, 04 Jan 2005 18:43:26 -0500	[thread overview]
Message-ID: <41DB2A1E.2020809@pobox.com> (raw)
In-Reply-To: <58cb370e05010314092d421aee@mail.gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> Existing IDE drivers are not going away any time soon (not 2.6.x at least)
> and if/when this happens we shouldn't drop CHS support completely
> from the kernel - IMHO it is quite easy to add CHS support to libata.
> I also agree that libata PATA development should be focused on LBA
> but I don't see any problem in keeping CHS support around...


I don't think it's a problem to support C/H/S in libata.  libata already 
has to handle lba28/lba48, CHS would simply be a third instance of the 
"fill read/write taskfile" code.

	Jeff



  reply	other threads:[~2005-01-04 23:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 10:42 libata PATA support - work items? Albert Lee
2005-01-01 19:19 ` Eric Mudama
2005-01-03 20:56   ` Greg Freemyer
2005-01-03 21:20     ` Eric Mudama
2005-01-03 22:09       ` Bartlomiej Zolnierkiewicz
2005-01-04 23:43         ` Jeff Garzik [this message]
2005-01-04 23:41   ` Jeff Garzik
2005-01-05  0:50     ` Alan Cox
2005-01-05  2:42       ` Jeff Garzik
2005-01-05  3:43         ` Alan Cox
2005-01-05 12:59       ` Bartlomiej Zolnierkiewicz
2005-01-04 23:32 ` Jeff Garzik
2005-01-06  8:51   ` Albert Lee
2005-01-06 21:29     ` Alan Cox
2005-01-06 23:07       ` Bartlomiej Zolnierkiewicz

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=41DB2A1E.2020809@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=albertcc@tw.ibm.com \
    --cc=bzolnier@gmail.com \
    --cc=dmares@dmares.com \
    --cc=dwm@maxeymade.com \
    --cc=edmudama@gmail.com \
    --cc=greg.freemyer@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).