From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: JosephChan@via.com.tw
Cc: alan@lxorguk.ukuu.org.uk, linux-ide@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH 1/2 v1] pata_via.c: support VX855 and future chips whose IDE controller use 0x0571.
Date: Fri, 16 Jan 2009 15:15:27 +0300 [thread overview]
Message-ID: <49707A5F.7030109@ru.mvista.com> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB8087EC5C6@exchtp03.taipei.via.com.tw>
Hello.
JosephChan@via.com.tw wrote:
>> The patch adds entries for 0xFFFF (is that really right) as a
>> bridge and
>> 0xC409 - I see nothing for 0x0571.
>>
>
> PCI_DEVICE_ID_VIA_ANON is used to stand for Unknown South Bridge for VX855
> and future chips, since the pata_via has a southbridge check, which is redundant.
If it was redundant, it wouldn't have been there...
> If we may VIA has a new SB with new bridge ID which in not in the check list, whose
> IDE controller is 0x0571. Linux default pata_via can not drive IDE controller of 402, since
> the southbridge check in pata_via can not pass.
>
> So we add PCI_DEVICE_ID_VIA_ANON to stand for our future southbridge,
> and this will help to pass southbridge check.
>
Why not just add the new and future SB device IDs to the list?
> Is it possible to do this way? And can it be acceptable in kernel policy?
>
I doubt it...
MBR, Sergei
next prev parent reply other threads:[~2009-01-16 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 13:04 [PATCH 1/2 v1] pata_via.c: support VX855 and future chips whose IDE controller use 0x0571 JosephChan
2009-01-15 13:40 ` Alan Cox
2009-01-16 0:57 ` JosephChan
2009-01-16 12:15 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-16 11:46 JosephChan
2009-01-16 14:34 ` Tejun Heo
2009-01-19 11:26 ` JosephChan
2009-01-22 1:19 ` Tejun Heo
2009-01-22 11:37 ` JosephChan
2009-01-22 23:35 ` Tejun Heo
2009-01-23 3:15 ` JosephChan
2009-01-23 3:33 ` Tejun Heo
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=49707A5F.7030109@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=JosephChan@via.com.tw \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).