From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 12/15] alim15x3: ->speedproc, filter out invalid modes passed from user-space
Date: Mon, 2 Jul 2007 20:55:13 +0200 [thread overview]
Message-ID: <200707022055.13683.bzolnier@gmail.com> (raw)
In-Reply-To: <46894478.9070808@garzik.org>
On Monday 02 July 2007, Jeff Garzik wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Monday 02 July 2007, Jeff Garzik wrote:
> >> Bartlomiej Zolnierkiewicz wrote:
> >>> This would brake setups which currently work OK, i.e. BIOS set things up
> >>> (reminds me about cmd64x vs broken MWDMA)...
> >>>
> >>> The RightThing(tm) to do is to fix alim15x3 driver to program DMA timings
> >>> (especially given that pata_ali seems to already contain the needed code).
> >> I am not ready to trust that pata_ali works as well as alim15x3 in all
> >> cases. Someone should test e.g. Alpha AXP systems with IDE (use
> >> alim15x3) to make sure all is well.
> >
> > Sure but there is no problem with the new code in alim15x3 being X86 until
> > it is verified to work with Alpha AXP machines etc...
>
> I'm not sure I follow. You now want to mark alim15x3 X86-only? Or add
> the new code inside #ifdef X86?
Add the new code inside #ifdef X86, marking alim15x3 X86-only would be
on over-kill...
> >> alim15x3 covers buggy, ugly, quirky chipsets. I consider that coverage
> >> in general highly fragile.
> >
> > and in case of MWDMA modes also highly dependent on BIOS settings
> > which very likely results in broken suspend/resume...
>
> Agreed. But I would rather verify that timing programming works on
> supported platforms, before expanding use of said new code?
Sure given that you have Alpha and Sparc machines handy for testing...
I don't so testing all supported platforms could take a while,
in the meantime X86 users could enjoy fixed suspend/resume support...
Thanks,
Bart
next prev parent reply other threads:[~2007-07-02 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 19:10 [PATCH 12/15] alim15x3: ->speedproc, filter out invalid modes passed from user-space Bartlomiej Zolnierkiewicz
2007-07-02 15:42 ` Sergei Shtylyov
2007-07-02 17:56 ` Bartlomiej Zolnierkiewicz
2007-07-02 18:00 ` Jeff Garzik
2007-07-02 18:41 ` Bartlomiej Zolnierkiewicz
2007-07-02 18:31 ` Jeff Garzik
2007-07-02 18:55 ` Bartlomiej Zolnierkiewicz [this message]
2007-07-02 19:13 ` Bartlomiej Zolnierkiewicz
2007-07-02 19:17 ` Jeff Garzik
2007-07-02 19:53 ` Bartlomiej Zolnierkiewicz
2007-07-02 19:22 ` Alan Cox
2007-07-02 19:20 ` Jeff Garzik
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=200707022055.13683.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.