public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	John Bradford <john@grabjohn.com>,
	Erik van Engelen <Info@vanE.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Errors on 2th ide channel of promise ultra100 tx2
Date: Fri, 27 Feb 2004 18:26:31 -0700	[thread overview]
Message-ID: <20040228012630.GA3074@codepoet.org> (raw)
In-Reply-To: <200402280220.22324.bzolnier@elka.pw.edu.pl>

On Sat Feb 28, 2004 at 02:20:22AM +0100, Bartlomiej Zolnierkiewicz wrote:
> > Dunno if I qualify as sufficiently 'really smart' enough but the
> > last time I put in the considerable effort needed to re-sync the
> > 2.4 and 2.6 IDE layers, and merge in the useful -ac bits that
> > never made it into mainstream, nothing whatsoever came of my
> > efforts...
> 
> Did you actually split and send out your patches? :)

Yes....
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0175.html

> > My 2.4.x patches are in daily use by a large group of people
> > and they work fine, for what it is worth.  My IDE merging
> > patches are the following:
> >
> >     http://codepoet.org/kernel/
> >
> >     020_ide_layer_2.4.22-ac4.bz2
> 
> Needs splitting and most of this stuff needs new re-sync with 2.6. :-(

Yup.  After splitting and submitting to no effect it was
less effort to maintain the lot as one big patch...

> >     021_ide_geom_hpa_capacity64.bz2
> 
> Now I remember why this wasn't applied.
> It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl
> (because changes way drive->cyls is calculated).
> We workaround-ed it in 2.6 by removing this ioctl. :)
> I think we really should do the same for 2.4.

I did just that but it was rejected by Alan Cox...
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0193.html

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2004-02-28  1:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 10:52 Errors on 2th ide channel of promise ultra100 tx2 Erik van Engelen
2004-02-27 18:46 ` Marcelo Tosatti
2004-02-27 18:20   ` John Bradford
2004-02-27 19:30     ` Marcelo Tosatti
2004-02-27 19:01       ` Alan Cox
2004-02-27 20:14         ` Bartlomiej Zolnierkiewicz
2004-02-27 22:44           ` Erik Andersen
2004-02-28  1:20             ` Bartlomiej Zolnierkiewicz
2004-02-28  1:26               ` Erik Andersen [this message]
2004-02-28 16:01                 ` Alan Cox
2004-02-28 20:25                   ` John Bradford
2004-02-27 22:51           ` Marcelo Tosatti
2004-02-28  0:04             ` Bartlomiej Zolnierkiewicz
2004-02-27 22:08         ` Erik Andersen
2004-02-27 19:50       ` Rene Herman
2004-02-28 12:13   ` Erik van Engelen
2004-03-03  8:24   ` Erik van Engelen

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=20040228012630.GA3074@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=Info@vanE.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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