* [PATCH] PCMCIA identification strings for Elan -- second attempt
@ 2006-11-20 13:04 Tony Olech
2006-11-20 17:49 ` Dominik Brodowski
2006-11-28 2:05 ` Dominik Brodowski
0 siblings, 2 replies; 7+ messages in thread
From: Tony Olech @ 2006-11-20 13:04 UTC (permalink / raw)
To: Dominik Brodowski
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
patch against linux kernel 2.6.18 to add PCMCIA identification strings
From: Tony Olech <tony.olech@elandigitalsystems.com>
In older versions of the linux kernel it was sufficient for the
16-bit PCMCIA card manufacturer to distribute or make available
a text configuration file along with the physical cards. Such a
file with an extension of ".conf" and placed in the /etc/pcmcia
very easily enabled new hardware without rebuilding the kernel,
however with the new scheme of things, having found no userland
solution to the problem of new 16bit pcmcia card identification
this patch enumerates Elan Digital Systems strings.
In addition, for the ID strings to result in the correct module
being loaded, the too wide matching criterion of the PDaudioCF
card needs to have the MANF_ID/CARD_ID numbers replaced by the
more specific PROD_ID1 and PROD_ID2 strings. It is unfortunate
that otherwise the pdaudiocf module is loaded whenever an ELAN
pcmcia card is inserted, resulting in various random lockups
--- ./sound/pcmcia/pdaudiocf/pdaudiocf.c.orig 2006-11-20 10:24:23.000000000 +0000
+++ ./sound/pcmcia/pdaudiocf/pdaudiocf.c 2006-11-20 10:33:46.000000000 +0000
@@ -299,7 +299,8 @@ static int pdacf_resume(struct pcmcia_de
* Module entry points
*/
static struct pcmcia_device_id snd_pdacf_ids[] = {
- PCMCIA_DEVICE_MANF_CARD(0x015d, 0x4c45),
+ /* this is too general PCMCIA_DEVICE_MANF_CARD(0x015d, 0x4c45), */
+ PCMCIA_DEVICE_PROD_ID12("Core Sound","PDAudio-CF",0x396d19d2,0x71717b49),
PCMCIA_DEVICE_NULL
};
MODULE_DEVICE_TABLE(pcmcia, snd_pdacf_ids);
--- ./drivers/serial/serial_cs.c.orig 2006-11-17 10:59:10.000000000 +0000
+++ ./drivers/serial/serial_cs.c 2006-11-17 10:59:54.000000000 +0000
@@ -787,6 +787,30 @@ static struct pcmcia_device_id serial_id
PCMCIA_DEVICE_CIS_PROD_ID123("ADVANTECH", "COMpad-32/85", "1.0", 0x96913a85, 0x8fbe92ae, 0x0877b627, "COMpad2.cis"),
PCMCIA_DEVICE_CIS_PROD_ID2("RS-COM 2P", 0xad20b156, "RS-COM-2P.cis"),
PCMCIA_DEVICE_CIS_MANF_CARD(0x0013, 0x0000, "GLOBETROTTER.cis"),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c1997.","SERIAL CARD: SL100 1.00.",0x19ca78af,0xf964f42b),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c1997.","SERIAL CARD: SL100",0x19ca78af,0x71d98e83),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c1997.","SERIAL CARD: SL232 1.00.",0x19ca78af,0x69fb7490),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c1997.","SERIAL CARD: SL232",0x19ca78af,0xb6bc0235),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c2000.","SERIAL CARD: CF232",0x63f2e0bd,0xb9e175d3),
+ PCMCIA_DEVICE_PROD_ID12("ELAN DIGITAL SYSTEMS LTD, c2000.","SERIAL CARD: CF232-5",0x63f2e0bd,0xfce33442),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: CF232",0x3beb8cf2,0x171e7190),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: CF232-5",0x3beb8cf2,0x20da4262),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: CF428",0x3beb8cf2,0xea5dd57d),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: CF500",0x3beb8cf2,0xd77255fa),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: IC232",0x3beb8cf2,0x6a709903),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: SL232",0x3beb8cf2,0x18430676),
+ PCMCIA_DEVICE_PROD_ID12("Elan","Serial Port: XL232",0x3beb8cf2,0x6f933767),
+ PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
+ PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
+ PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
+ PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
+ PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial+Parallel Port: SP230",0x3beb8cf2,0xdb9e58bc),
+ PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
+ PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
+ PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
+ PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
+ PCMCIA_MFC_DEVICE_PROD_ID12(2,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
+ PCMCIA_MFC_DEVICE_PROD_ID12(3,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
/* too generic */
/* PCMCIA_MFC_DEVICE_MANF_CARD(0, 0x0160, 0x0002), */
/* PCMCIA_MFC_DEVICE_MANF_CARD(1, 0x0160, 0x0002), */
--- ./drivers/parport/parport_cs.c.orig 2006-11-17 10:57:55.000000000 +0000
+++ ./drivers/parport/parport_cs.c 2006-11-17 10:58:52.000000000 +0000
@@ -263,6 +263,7 @@ void parport_cs_release(struct pcmcia_de
static struct pcmcia_device_id parport_ids[] = {
PCMCIA_DEVICE_FUNC_ID(3),
+ PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial+Parallel Port: SP230",0x3beb8cf2,0xdb9e58bc),
PCMCIA_DEVICE_MANF_CARD(0x0137, 0x0003),
PCMCIA_DEVICE_NULL
};
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-20 13:04 [PATCH] PCMCIA identification strings for Elan -- second attempt Tony Olech
@ 2006-11-20 17:49 ` Dominik Brodowski
2006-11-21 8:53 ` Tony Olech
2006-11-28 2:05 ` Dominik Brodowski
1 sibling, 1 reply; 7+ messages in thread
From: Dominik Brodowski @ 2006-11-20 17:49 UTC (permalink / raw)
To: Tony Olech
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
Hi,
Patch looks good, except:
> + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
> + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
> + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
> + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial+Parallel Port: SP230",0x3beb8cf2,0xdb9e58bc),
> + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
> + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
> + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
> + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> + PCMCIA_MFC_DEVICE_PROD_ID12(2,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> + PCMCIA_MFC_DEVICE_PROD_ID12(3,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
does the SL432 device have four independent multifunction subdevices? This
would be something I haven't seen before, and which would likely not work
with current code...
Thanks,
Dominik
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-20 17:49 ` Dominik Brodowski
@ 2006-11-21 8:53 ` Tony Olech
2006-11-21 13:28 ` Dominik Brodowski
0 siblings, 1 reply; 7+ messages in thread
From: Tony Olech @ 2006-11-21 8:53 UTC (permalink / raw)
To: Dominik Brodowski
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
YES is does indeed have 4 serial channels.
Tony Olech
---------------------------------------------------------
On Mon, 2006-11-20 at 12:49 -0500, Dominik Brodowski wrote:
> Hi,
>
> Patch looks good, except:
>
> > + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(0,"Elan","Serial+Parallel Port: SP230",0x3beb8cf2,0xdb9e58bc),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: CF332",0x3beb8cf2,0x16dc1ba7),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL332",0x3beb8cf2,0x19816c41),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL385",0x3beb8cf2,0x64112029),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(1,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(2,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
> > + PCMCIA_MFC_DEVICE_PROD_ID12(3,"Elan","Serial Port: SL432",0x3beb8cf2,0x1cce7ac4),
>
> does the SL432 device have four independent multifunction subdevices? This
> would be something I haven't seen before, and which would likely not work
> with current code...
>
> Thanks,
> Dominik
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-21 8:53 ` Tony Olech
@ 2006-11-21 13:28 ` Dominik Brodowski
2006-11-21 13:58 ` Tony Olech
0 siblings, 1 reply; 7+ messages in thread
From: Dominik Brodowski @ 2006-11-21 13:28 UTC (permalink / raw)
To: Tony Olech
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
On Tue, Nov 21, 2006 at 08:53:22AM +0000, Tony Olech wrote:
> YES is does indeed have 4 serial channels.
Four serial channels might be handled by two device functions... and it's
the number of device function which decides whether it is a "MFC" device or
not. And if it indeed has four sub-devices, the PCMCIA core needs to be
improved -- therefore, could you send me a CIS dump for this device, please?
Thanks,
Dominik
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-21 13:28 ` Dominik Brodowski
@ 2006-11-21 13:58 ` Tony Olech
2006-11-28 2:04 ` Dominik Brodowski
0 siblings, 1 reply; 7+ messages in thread
From: Tony Olech @ 2006-11-21 13:58 UTC (permalink / raw)
To: Dominik Brodowski
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
Hi,
I can't find an actual device, and my former boss
left Elan a few months ago, but I have attached
the data from our product database:
cis configuration file:
[-- Attachment #2: SL432.TXT --]
[-- Type: text/plain, Size: 4374 bytes --]
;****************************************************************************************
;*
;* Filename: sl432.txt
;*
;* Author: P. Sleeman Elan Digital Systems Limited (c) 2003
;*
;* Date: 19/05/2003
;*
;* Description: This file defines the CIS for the SL432 PC Card
;*
;* File Revision: 1.01
;*
;* History: Rev. Date Revision History
;* 1.00 19/05/2003 Creation
;*
;****************************************************************************************
$01 $03 $00 $00 $FF
$15 $3A $05 $00 [Elan] $00 [Serial Port: SL432] $00 [1.00] $00 [KIT:Kxxxxx-xxx ] $00 $FF
$20 $04 $5D $01 [EL]
$06 $15 $04 $00 $60 $00 $00 $00 $00 $B0 $00 $00 $00 $00 $00 $01 $00 $00 $00 $60 $01 $00 $00 ;long link MFC, 4 functions
%60 ;pad to here with 0xffs. Start of function 1's CIS
$13 $03 [CIS] ;link target tuple
$21 $02 $02 $01 ;identify as a serial port
$1A $05 $01 $27 $00 $04 $61 ;2 byte config base,1 byte ccr presence mask, last table index is 27h, 400h base, cor, csr, iobase0&1 present
;$1B $0D $C7 $01 $19 $01 $55 $AB $60 $F8 $03 $07 $B0 $FF $FF ;com1 default settings: 5V, 3f8, IRQ share lvl & an IRQ mask = irq any
;$1B $0B $8F $01 $18 $AB $60 $F8 $02 $07 $B0 $FF $FF ;com2 2f8 irq any
;$1B $0B $97 $01 $18 $AB $60 $E8 $03 $07 $B0 $FF $FF ;com3 3E8 irq any
;$1B $0B $9F $01 $18 $AB $60 $E8 $02 $07 $B0 $FF $FF ;com4 2E8 irq any
$1B $07 $A7 $01 $18 $23 $B0 $FF $FF ;comN any io on 8 byte boundary, lvl irq any in mask ffff
$FF ;end of this function's CIS
%B0 ;pad to here with 0xffs. Start of function 2's CIS
$13 $03 [CIS] ;link target tuple
$21 $02 $02 $01 ;identify as a serial port
$1A $05 $01 $27 $20 $04 $61 ;2 byte config base,1 byte ccr presence mask, last table index is 27h, 420h base, cor, csr, iobase0&1 present
;$1B $0D $CF $01 $19 $01 $55 $AB $60 $F8 $02 $07 $B0 $FF $FF ;com2 default settings: 5V, 2f8, IRQ share lvl & an IRQ mask = irq any
;$1B $0B $87 $01 $18 $AB $60 $F8 $03 $07 $B0 $FF $FF ;com1 3f8 irq any
;$1B $0B $9F $01 $18 $AB $60 $E8 $02 $07 $B0 $FF $FF ;com4 2e8 irq any
;$1B $0B $97 $01 $18 $AB $60 $E8 $03 $07 $B0 $FF $FF ;com3 3e8 irq any
$1B $07 $A7 $01 $18 $23 $B0 $FF $FF ;comN any io on 8 byte boundary, lvl irq any in mask ffff
$FF ;end of this function's CIS
%100 ;pad to here with 0xffs. Start of function 3's CIS
$13 $03 [CIS] ;link target tuple
$21 $02 $02 $01 ;identify as a serial port
$1A $05 $01 $27 $40 $04 $61 ;2 byte config base,1 byte ccr presence mask, last table index is 27h, 400h base, cor, csr, iobase0&1 present
;$1B $0D $D7 $01 $19 $01 $55 $AB $60 $E8 $03 $07 $B0 $FF $FF ;com3 3E8 irq any
;$1B $0B $9F $01 $18 $AB $60 $E8 $02 $07 $B0 $FF $FF ;com4 2E8 irq any
;$1B $0B $87 $01 $18 $AB $60 $F8 $03 $07 $B0 $FF $FF ;com1 default settings: 5V, 3f8, IRQ share lvl & an IRQ mask = irq any
;$1B $0B $8F $01 $18 $AB $60 $F8 $02 $07 $B0 $FF $FF ;com2 2f8 irq any
$1B $07 $A7 $01 $18 $23 $B0 $FF $FF ;comN any io on 8 byte boundary, lvl irq any in mask ffff
$FF ;end of this function's CIS
%160 ;pad to here with 0xffs. Start of function 4's CIS
$13 $03 [CIS] ;link target tuple
$21 $02 $02 $01 ;identify as a serial port
$1A $05 $01 $27 $60 $04 $61 ;2 byte config base,1 byte ccr presence mask, last table index is 27h, 400h base, cor, csr, iobase0&1 present
;$1B $0D $DF $01 $19 $01 $55 $AB $60 $E8 $02 $07 $B0 $FF $FF ;com4 2E8 irq any
;$1B $0B $97 $01 $18 $AB $60 $E8 $03 $07 $B0 $FF $FF ;com3 3E8 irq any
;$1B $0B $87 $01 $18 $AB $60 $F8 $03 $07 $B0 $FF $FF ;com1 default settings: 5V, 3f8, IRQ share lvl & an IRQ mask = irq any
;$1B $0B $8F $01 $18 $AB $60 $F8 $02 $07 $B0 $FF $FF ;com2 2f8 irq any
$1B $07 $A7 $01 $18 $23 $B0 $FF $FF ;comN any io on 8 byte boundary, lvl irq any in mask ffff
$FF ;end of this function's CIS
$FF $FF
$80 $11 [<DATE>dd.mm.yyyy] $00
$81 $2E [Copyright (c) Elan Digital Systems Ltd, 2003.] $00
%200 ;make the file 512 bytes long
\x1a
[-- Attachment #3: Type: text/plain, Size: 16 bytes --]
the binary cis:
[-- Attachment #4: SL432.CIS --]
[-- Type: application/octet-stream, Size: 512 bytes --]
[-- Attachment #5: Type: text/plain, Size: 21 bytes --]
the dump_cis_output:
[-- Attachment #6: SL432.DUMP_CIS --]
[-- Type: application/octet-stream, Size: 1517 bytes --]
offset 0x02, tuple 0x01, link 0x03
00 00 ff
dev_info
NULL 0ns, 512b
offset 0x07, tuple 0x15, link 0x3a
05 00 45 6c 61 6e 00 53 65 72 69 61 6c 20 50 6f
72 74 3a 20 53 4c 34 33 32 00 31 2e 30 30 00 4b
49 54 3a 4b 78 78 78 78 78 2d 78 78 78 20 20 20
20 20 20 20 20 20 20 20 00 ff
vers_1 5.0, "Elan", "Serial Port: SL432", "1.00",
"KIT:Kxxxxx-xxx "
offset 0x43, tuple 0x20, link 0x04
5d 01 45 4c
manfid 0x015d, 0x4c45
offset 0x49, tuple 0x06, link 0x15
04 00 60 00 00 00 00 b0 00 00 00 00 00 01 00 00
00 60 01 00 00
mfc_long_link
function 0: attr 0x0060
function 1: attr 0x00b0
function 2: attr 0x0100
function 3: attr 0x0160
offset 0x60, tuple 0xff, link 0xff
13 03 43 49 53 21 02 02 01 1a 05 01 27 00 04 61
1b 07 a7 01 18 23 b0 ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
13 03 43 49 53 21 02 02 01 1a 05 01 27 20 04 61
1b 07 a7 01 18 23 b0 ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
13 03 43 49 53 21 02 02 01 1a 05 01 27 40 04 61
1b 07 a7 01 18 23 b0 ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[-- Attachment #7: Type: text/plain, Size: 625 bytes --]
Tony Olech
Elan Digital Systems Limited
------------------------------------------------------------------------
On 21 Nov 2006, at 13:28, Dominik Brodowski wrote:
> On Tue, Nov 21, 2006 at 08:53:22AM +0000, Tony Olech wrote:
>> YES is does indeed have 4 serial channels.
>
> Four serial channels might be handled by two device functions...
> and it's
> the number of device function which decides whether it is a "MFC"
> device or
> not. And if it indeed has four sub-devices, the PCMCIA core needs
> to be
> improved -- therefore, could you send me a CIS dump for this
> device, please?
>
> Thanks,
> Dominik
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-21 13:58 ` Tony Olech
@ 2006-11-28 2:04 ` Dominik Brodowski
0 siblings, 0 replies; 7+ messages in thread
From: Dominik Brodowski @ 2006-11-28 2:04 UTC (permalink / raw)
To: Tony Olech
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
On Tue, Nov 21, 2006 at 01:58:31PM +0000, Tony Olech wrote:
> Hi,
> I can't find an actual device, and my former boss
> left Elan a few months ago, but I have attached
> the data from our product database:
Thanks!
Dominik
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] PCMCIA identification strings for Elan -- second attempt
2006-11-20 13:04 [PATCH] PCMCIA identification strings for Elan -- second attempt Tony Olech
2006-11-20 17:49 ` Dominik Brodowski
@ 2006-11-28 2:05 ` Dominik Brodowski
1 sibling, 0 replies; 7+ messages in thread
From: Dominik Brodowski @ 2006-11-28 2:05 UTC (permalink / raw)
To: Tony Olech
Cc: Linux kernel development, PCMCIA Maintainence, David Hinds,
Jaroslav Kysela, Bart Prescott
On Mon, Nov 20, 2006 at 01:04:39PM +0000, Tony Olech wrote:
> patch against linux kernel 2.6.18 to add PCMCIA identification strings
> From: Tony Olech <tony.olech@elandigitalsystems.com>
>
> In older versions of the linux kernel it was sufficient for the
> 16-bit PCMCIA card manufacturer to distribute or make available
> a text configuration file along with the physical cards. Such a
> file with an extension of ".conf" and placed in the /etc/pcmcia
> very easily enabled new hardware without rebuilding the kernel,
> however with the new scheme of things, having found no userland
> solution to the problem of new 16bit pcmcia card identification
> this patch enumerates Elan Digital Systems strings.
>
> In addition, for the ID strings to result in the correct module
> being loaded, the too wide matching criterion of the PDaudioCF
> card needs to have the MANF_ID/CARD_ID numbers replaced by the
> more specific PROD_ID1 and PROD_ID2 strings. It is unfortunate
> that otherwise the pdaudiocf module is loaded whenever an ELAN
> pcmcia card is inserted, resulting in various random lockups
Applied to pcmcia-2.6, thanks.
Dominik
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-11-28 2:05 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-20 13:04 [PATCH] PCMCIA identification strings for Elan -- second attempt Tony Olech
2006-11-20 17:49 ` Dominik Brodowski
2006-11-21 8:53 ` Tony Olech
2006-11-21 13:28 ` Dominik Brodowski
2006-11-21 13:58 ` Tony Olech
2006-11-28 2:04 ` Dominik Brodowski
2006-11-28 2:05 ` Dominik Brodowski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox