mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre2aa2
Date: Tue, 12 Mar 2002 09:11:14 +0100	[thread overview]
Message-ID: <20020312081114.GA704@suse.de> (raw)
In-Reply-To: <20020311082031.B10413@dualathlon.random> <E16kRp6-0000rR-00@the-village.bc.nu> <20020311230729.I10413@dualathlon.random>
In-Reply-To: <20020311230729.I10413@dualathlon.random>

On Mon, Mar 11 2002, Andrea Arcangeli wrote:
> On Mon, Mar 11, 2002 at 03:34:52PM +0000, Alan Cox wrote:
> > > Only in 2.4.19pre2aa2: 00_amd-viper-7441-guessed-1
> > > 
> > > 	Let amd74xx recognize the 7441 amd chipset, it works and I needed it
> > > 	mainly to set ->highmem = 1 and to skip the bounce buffers on my
> > > 	desktop.  (Tried also mode 5 and it failed, so I #undef __CAN_MODE_5
> > > 	back)
> > 
> > The correct AMD 7441 fixes are in the IDE patch and have been for a few
> > months. They were supplied by AMD and work a treat. I don't believe there is
> > any reason they require the new IDE infrastructure. They are howeve 32bit
> > still so the 64bit IDE will be nice
> 
> thanks for the info. I will merge the IDE patch then (with the
> additional modification to enable high-IO, that is why I looked into
> it). btw, while making that change, I was also wondering that it would
> be simpler to enable the highio in the common ide-dma part, rather than
> in the chipsets tunings, the highio is completly unrelated to the fact
> we compile amd7xxx or viaxxx into the kernel or not. but I didn't made
> that change because the amd7xxx driver was working fine for me and also
> because of possibly broken chipsets with the 31th bit of the bus address
> disconnected, just to stay on the very safe side and not to trigger
> hardware (not software) bugs.

We can probably safely just drop the highio flag in the hwif now. I just
added it way back then as a safeguard, it might be a better idea to just
have potentially buggy chipsets set their dma mask appropriately and let
ide-dma enable the right bounce address (if any).

I'll update the block-highmem for 2.4.19-pre3 now that the IDE merge is
in.

-- 
Jens Axboe


  reply	other threads:[~2002-03-12  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11  7:20 2.4.19pre2aa2 Andrea Arcangeli
2002-03-11 15:34 ` 2.4.19pre2aa2 Alan Cox
2002-03-11 22:07   ` 2.4.19pre2aa2 Andrea Arcangeli
2002-03-12  8:11     ` Jens Axboe [this message]
2002-03-12 10:05       ` 2.4.19pre2aa2 Andrea Arcangeli

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=20020312081114.GA704@suse.de \
    --to=axboe@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®