Bug#634180: ahci and device ID 236f
* Ben Hutchings b...@decadent.org.uk [2012-09-10 01:09]: And can you put it into the Debian kernel? I suppose we need this in both squeeze and wheezy, right? Yes, that'd be great. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634180: ahci and device ID 236f
On Sat, 2012-09-08 at 11:26 +0100, Martin Michlmayr wrote: * Ben Hutchings b...@decadent.org.uk [2011-07-18 02:03]: Sounds reasonable. This needs to go upstream as well, if it hasn't done so already. Hi Ben, A user just reminded me that this is still outstanding. I can see from tre bug log that you sent the patch to Jeff/linux-...@vger.kernel.org but I cannot find it in the linux-ide mailing list archives, so maybe it wasn't sent... Can you re-send it to Jeff/linux-ide please? And can you put it into the Debian kernel? I suppose we need this in both squeeze and wheezy, right? Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert. signature.asc Description: This is a digitally signed message part
Bug#634180: ahci and device ID 236f
* Ben Hutchings b...@decadent.org.uk [2011-07-18 02:03]: Sounds reasonable. This needs to go upstream as well, if it hasn't done so already. Hi Ben, A user just reminded me that this is still outstanding. I can see from tre bug log that you sent the patch to Jeff/linux-...@vger.kernel.org but I cannot find it in the linux-ide mailing list archives, so maybe it wasn't sent... Can you re-send it to Jeff/linux-ide please? And can you put it into the Debian kernel? Thanks. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634180: ahci and device ID 236f
Package: linux-2.6 Version: 2.6.32-35 Two users reported on debian-arm [1] that eSATA doesn't work on their new QNAP TS-219P+ devices. In older TS-219P+ models, lspci says: 00:01.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 00:01.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) But in the new model, it says: 00:01.0 IDE interface: JMicron Technology Corp. Device 236f (rev 03) I'm not sure why only IDE is shown and not SATA since the chip is used for eSATA. A user said: I can confirm this on my TS-219P+ which I bought in May. But the Chip itself has JMB362 printed on it which normally should have device ID 2362. I confirmed with QNAP that the new models use a slightly newer chip. QNAP uses the following patch. The Debian user confirmed that eSATA works with this patch. linux-2.6.33.2/drivers/ata/ahci.c { PCI_VDEVICE(INTEL, 0x3b2f), board_ahci }, /* PCH AHCI */ /* JMicron 360/1/3/5/6, match class to avoid IDE function */ +//QNAP patch support JM362B JM362C + { PCI_VDEVICE(JMICRON, 0x236f), board_ahci_ign_iferr }, + { PCI_VDEVICE(JMICRON, 0x2362), board_ahci_ign_iferr }, + { PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_CLASS_STORAGE_SATA_AHCI, 0xff, board_ahci_ign_iferr }, [1] http://lists.debian.org/debian-arm/2011/06/msg00077.html -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634180: ahci and device ID 236f
On Sun, 2011-07-17 at 14:41 +0100, Martin Michlmayr wrote: Package: linux-2.6 Version: 2.6.32-35 Two users reported on debian-arm [1] that eSATA doesn't work on their new QNAP TS-219P+ devices. In older TS-219P+ models, lspci says: 00:01.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 00:01.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) But in the new model, it says: 00:01.0 IDE interface: JMicron Technology Corp. Device 236f (rev 03) I'm not sure why only IDE is shown and not SATA since the chip is used for eSATA. That first part is based on the PCI class code. Maybe they used the wrong class code. However, most PCI drivers do not match devices by class code and this probably doesn't matter. A user said: I can confirm this on my TS-219P+ which I bought in May. But the Chip itself has JMB362 printed on it which normally should have device ID 2362. I confirmed with QNAP that the new models use a slightly newer chip. QNAP uses the following patch. The Debian user confirmed that eSATA works with this patch. [...] Sounds reasonable. This needs to go upstream as well, if it hasn't done so already. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part