mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mru@inprovide.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] PCI: PCI quirk for Asus A8V and A8V Deluxe motherboards
Date: Sun, 19 Mar 2006 12:58:50 +0000	[thread overview]
Message-ID: <yw1xd5gi381h.fsf@agrajag.inprovide.com> (raw)
In-Reply-To: <dvjcb4$as2$1@sea.gmane.org>

Andras Mantia <amantia@kde.org> writes:

> Måns Rullgård wrote:
>> Hmm, mine crashed when I used the PCI card.  Using the onboard sound
>> was fine.
>
> Now it doesn't crash. :-0 That hang was with kernel 2.6.15, but I switeched
> back to 2.6.13 as that is what suse provides and I played some music on
> both cards and tried Skype on the onboard card (there was the hang) and it
> was OK.

Just write it off to cosmic rays if it doesn't happen again.

>>>>> Can you tell me how can I find the real device ID for my chipset? It
>>>>> *should* be the same one as the original writer of the patch wrote (he
>>>>> also had an ASUS A8V Deluxe as I understood), but the experience tells
>>>>> it is not.
>>>> 
>>>> lspci -n will list the PCI IDs in hex.
>>>
>>> Thanks.
>> 
>> Care to post the output?
>
> Sure. I still don't know how to use those numbers in the quircks.c  (do I
> need to create something like #define PCI_DEVICE_WHATEVER pciIDNumber ?).

The device IDs are already #defined in <linux/pci_ids.h>.

> The result of lspci -vvvn is attached.

> 00:11.0 Class 0601: 1106:3227
> 	Subsystem: 1043:80ed

This is the interesting bit.  Curiously enough, it is exactly the same
as mine.  I can't see any reason why it shouldn't match on your board.

Try sticking some printk()s in there and find out what values are
actually seen.

-- 
Måns Rullgård
mru@inprovide.com


  reply	other threads:[~2006-03-19 12:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-05 19:27 bjd
2006-03-05 19:34 ` Dave Jones
2006-03-05 20:32 ` Lee Revell
2006-03-06  9:34   ` Jan-Benedict Glaw
2006-03-05 21:24 ` Måns Rullgård
2006-03-11 19:49   ` Måns Rullgård
2006-03-17 10:38 ` Andras Mantia
2006-03-17 14:33   ` Jan-Benedict Glaw
2006-03-17 14:43     ` Andras Mantia
2006-03-17 14:49       ` Jan-Benedict Glaw
2006-03-17 18:18         ` Andras Mantia
2006-03-17 19:29           ` Måns Rullgård
2006-03-18 14:01             ` Andras Mantia
2006-03-18 14:23               ` Måns Rullgård
2006-03-18 15:00                 ` Andras Mantia
2006-03-18 15:58                   ` Måns Rullgård
2006-03-19 10:38                     ` Andras Mantia
2006-03-19 12:58                       ` Måns Rullgård [this message]
2006-03-19 15:11                         ` Andras Mantia
2006-03-19 16:35                           ` Måns Rullgård
2006-03-19 17:38                             ` Andras Mantia
2006-03-19 18:03                               ` Måns Rullgård
2006-03-19 18:18                                 ` Andras Mantia
2006-03-19 18:36                                   ` Måns Rullgård
2006-03-19 18:44                                     ` Andras Mantia
2006-03-17 19:15       ` Måns Rullgård
  -- strict thread matches above, loose matches on Subject: below --
2006-03-05 12:37 Bauke jan Douma
2006-02-12  2:22 bjd

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=yw1xd5gi381h.fsf@agrajag.inprovide.com \
    --to=mru@inprovide.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®