From: Pierre Ossman <pierre@ossman.eu>
To: Harald Welte <HaraldWelte@viatech.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sdhci: Specific quirk vor VIA SDHCI controller in VX855ES
Date: Sun, 21 Jun 2009 20:56:31 +0200 [thread overview]
Message-ID: <20090621205631.067429de@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090619222828.GA4664@prithivi.gnumonks.org>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Sat, 20 Jun 2009 00:28:28 +0200
Harald Welte <HaraldWelte@viatech.com> wrote:
> Hi!
>
> On Fri, Jun 19, 2009 at 09:33:14PM +0200, Pierre Ossman wrote:
>
> > Does this block have a name? Something nicer than 0x95d0 in the id list
> > would be nice.
>
> Unfortunately no. We really have a big mess with those integrated chipsets
> that have something like 15 PCI devices inside one component. We cannot call
> all of them 'VX855'. or 'VX800', as that would clash. Naming things
> 'PCI_DEVICE_VIA_VX800_SDHCI' is also not really correct, since the same
> block appearas in other integrated chipsets, too.
>
> As for VIA's documentation, every block is called something like D13F3 (pci
> device 13 function 3), which doesn't really sound all that much better than
> just putting a 0x95d0 there.
>
> To make things even furter complicated, some VIA Docs refer to the SDHCI
> controller as 'SDIO controller' and the via-sdmmc as 'SD card controller'...
>
Sounds like you guys need an official code name department. :)
I've queued up the patch.
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-06-21 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 14:53 Harald Welte
2009-06-19 19:33 ` Pierre Ossman
2009-06-19 22:28 ` Harald Welte
2009-06-21 18:56 ` Pierre Ossman [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=20090621205631.067429de@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=HaraldWelte@viatech.com \
--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®