All of lore.kernel.org
 help / color / mirror / Atom feed
From: Velu Erwan <erwan@seanodes.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Bruno Harbulot <bruno_harbulot@yahoo.co.uk>, linux-ide@vger.kernel.org
Subject: Re: ATIIXP and libata
Date: Fri, 02 Dec 2005 11:54:38 +0100	[thread overview]
Message-ID: <439027EE.6010202@seanodes.com> (raw)
In-Reply-To: <58cb370e0511040217y778fab7cj47d198b53126f9d7@mail.gmail.com>

Bartlomiej Zolnierkiewicz a écrit :

>  
>
>>(I don't know much about the subject, but I presume that workarounds to
>>get ata_id_is_sata "to work somehow" from atiixp.c would not be the
>>right thing to do, even if feasible.)
>>    
>>
>
><linux/ata.h> include is used by both IDE and libata
>driver, however ata_id_is_sata() shouldn't be used
>directly in atiixp.c but similar check should be added
>to eighty_ninty_three() from ide-iops.c.
>  
>
Is there any chance to have a fix for this troubles in some recent kernel ?
I don't know how to help to make this fixed upstream. I would like not 
to have a personnal patch for making my system running.

Erwan,

      parent reply	other threads:[~2005-12-02 10:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 23:53 ATIIXP and libata Bruno Harbulot
2005-11-04  9:16 ` Velu Erwan
2005-11-04 10:09   ` Bartlomiej Zolnierkiewicz
2005-11-05 15:32   ` Bruno Harbulot
2005-11-04 10:17 ` Bartlomiej Zolnierkiewicz
2005-11-05 15:27   ` [PATCH] " Bruno Harbulot
2006-05-31 22:00     ` Velu Erwan
2006-06-07  7:36       ` Nobody cares about the ATIIXP troubles reported since October ? Velu Erwan
2006-06-12 22:23         ` Bruno Harbulot
2006-06-12 22:32       ` [PATCH] Re: ATIIXP and libata Randy.Dunlap
2006-06-19  8:12         ` Velu Erwan
2006-06-19 17:27           ` Randy.Dunlap
2006-06-20  8:57             ` Velu Erwan
2006-06-20 16:57               ` Randy.Dunlap
2005-12-02 10:54   ` Velu Erwan [this message]

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=439027EE.6010202@seanodes.com \
    --to=erwan@seanodes.com \
    --cc=bruno_harbulot@yahoo.co.uk \
    --cc=bzolnier@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 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.