Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only

2007-10-13 Thread Magnus Holmgren
tags 435547 + d-i thanks Hi! Can this be fixed for the next Debian Etch point release, especially so that Debian can be net-installed on computers with this hardware? Now, I have a laptop with SiS 968, not SiS 966, so you'll even need something like isa_bridge =

Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only

2007-08-02 Thread dann frazier
On Wed, Aug 01, 2007 at 04:18:35PM +0200, Neil Muller wrote: Package: linux-source-2.6.18 Severity: normal Tags: patch The sis190 driver uses the ISA bridge to read various values. It currently assumes that the bridge is Sis965 only, but recent SIS motherboards use the Sis966 bridge. The

Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only

2007-08-02 Thread maximilian attems
forwarded 435547 [EMAIL PROTECTED] stop On Thu, Aug 02, 2007 at 09:41:19AM -0600, dann frazier wrote: On Wed, Aug 01, 2007 at 04:18:35PM +0200, Neil Muller wrote: Package: linux-source-2.6.18 Severity: normal Tags: patch The sis190 driver uses the ISA bridge to read various values. It

Processed: Re: Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only

2007-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: forwarded 435547 [EMAIL PROTECTED] Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] stop Stopping processing here. Please contact me

Bug#435547: linux-source-2.6.18: sis190 driver should not assume ISA bridge is SiS965 only

2007-08-01 Thread Neil Muller
Package: linux-source-2.6.18 Severity: normal Tags: patch The sis190 driver uses the ISA bridge to read various values. It currently assumes that the bridge is Sis965 only, but recent SIS motherboards use the Sis966 bridge. The following patch (against linux-source-2.6.18) should address this.