From: Andrew Hutchings <info@a-wing.co.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org, vinay kumar <b4uvin@yahoo.co.in>,
jgarzik@pobox.com
Subject: Re: sis190
Date: Fri, 10 Jun 2005 14:55:25 +0100 [thread overview]
Message-ID: <42A99BCD.8000901@a-wing.co.uk> (raw)
In-Reply-To: <20050609211843.GA5630@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Andrew Hutchings <info@a-wing.co.uk> :
> [...]
>
>>Tried it, it didn't detect the sis190 in this board so I changed the
>>PCI_ID lines to:
>>static struct pci_device_id sis190_pci_tbl[] __devinitdata = {
>> { 0x1039, 0x0190, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
>> { 0,},
>>};
>
>
> /me scratches head
>
> The figures look the same. I must be tired.
>
I thought so, but for some reason it makes a difference.
>
>>This then detected it but caused a soft lockup on modprobe with a dump
>>which I have attached here. I have also attched lspci -vvv and -xxx for
>>you.
>
>
> Right, there was a bug. I am not sure the fix will really fix though.
>
> See the patch of the day:
>
> http://www.fr.zoreil.com/people/francois/misc/20050610-2.6.12-rc-sis190-test.patch
>
> Please add a dmesg as well if something goes wrong.
>
Something went wrong on build. Getting 'syntax error before '}' token'
on every line there is _msleep(1);
Regards
Andrew
--
Andrew Hutchings (A-Wing)
Linux Guru - Netserve Consultants Ltd. - http://www.domaincity.co.uk/
Admin - North Wales Linux User Group - http://www.nwlug.org.uk/
BOFH excuse 311: transient bus protocol violation
next prev parent reply other threads:[~2005-06-10 13:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 22:37 sis5513.c patch Andrew Hutchings
2005-06-07 22:57 ` Francois Romieu
2005-06-07 23:20 ` Andrew Hutchings
2005-06-08 22:51 ` sis190 (was: Re: sis5513.c patch) Francois Romieu
2005-06-09 4:54 ` sis190 Andrew Hutchings
2005-06-09 12:02 ` sis190 Andrew Hutchings
2005-06-09 21:18 ` sis190 Francois Romieu
2005-06-10 13:55 ` Andrew Hutchings [this message]
2005-06-10 23:41 ` sis190 Francois Romieu
2005-06-09 15:17 ` sis5513.c patch Vojtech Pavlik
2005-06-08 7:27 ` Bartlomiej Zolnierkiewicz
2005-06-08 8:23 ` Andrew Hutchings
2005-06-08 8:58 ` Bartlomiej Zolnierkiewicz
2005-06-08 9:14 ` Bartlomiej Zolnierkiewicz
2005-06-08 9:28 ` Andrew Hutchings
2005-06-08 10:28 ` Andrew Hutchings
-- strict thread matches above, loose matches on Subject: below --
2005-06-11 9:39 sis190 Pascal CHAPPERON
2005-06-11 10:56 ` sis190 Francois Romieu
2005-06-13 8:19 sis190 Pascal CHAPPERON
2005-06-13 21:39 ` sis190 Francois Romieu
2005-06-14 14:14 sis190 Pascal CHAPPERON
2005-06-14 20:04 ` sis190 Francois Romieu
2005-06-15 15:22 sis190 Pascal CHAPPERON
2005-06-16 22:34 ` sis190 Francois Romieu
2005-06-17 11:14 sis190 Pascal CHAPPERON
2005-06-17 18:22 ` sis190 Francois Romieu
2005-06-19 10:17 sis190 Pascal CHAPPERON
2005-06-21 23:02 ` sis190 Francois Romieu
2005-06-26 12:39 sis190 Pascal CHAPPERON
2005-06-30 23:37 ` sis190 Francois Romieu
2005-07-02 10:52 sis190 Pascal CHAPPERON
2005-07-02 11:33 ` sis190 Francois Romieu
2005-07-04 23:30 ` sis190 Francois Romieu
2005-07-06 15:58 sis190 Pascal CHAPPERON
2005-07-06 21:29 ` sis190 Francois Romieu
2005-07-09 13:25 sis190 Pascal CHAPPERON
2005-07-09 20:57 ` sis190 Francois Romieu
2005-07-10 13:23 sis190 Pascal CHAPPERON
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=42A99BCD.8000901@a-wing.co.uk \
--to=info@a-wing.co.uk \
--cc=b4uvin@yahoo.co.in \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox