Hi Randy and list, thanks for the extensive reply. I'll try to answer and comment below:
Randy.Dunlap wrote:
1. Don't change struct { ... } ati_remote_tbl to a typedef. In general, Linux doesn't like or use typedefs for structures. It hides too much. Leave a struct as a struct.
Can you tell me how to use to the same struct then? I'm a bit more into C++ then C. Was that refering the same struct again? I'll give it a try.
Uh, it's trivial. Mostly use 'struct ati_remote_tbl' anywhere that you had used ati_remote_tbl_t.
use:
struct ati_remote_tbl
{
short kind;
unsigned char data1, data2;
int type;
unsigned int code;
int value;
};
instead of your typedef.Change: static ati_remote_tbl_t ati_remote_tbl_general[] = to static struct ati_remote_tbl ati_remote_tbl_general[] =
and change: static ati_remote_tbl_t ati_remote_tbl_medion[] = to static struct ati_remote_tbl ati_remote_tbl_medion[] =
Same for medion2 table.
Change:
ati_remote_tbl_t* key_tbl;
to
struct ati_remote_tbl *key_tbl;Change:
static int ati_remote_event_lookup( ati_remote_tbl_t* key_tbl, int rem, unsigned char d1, unsigned char d2)
to
static int ati_remote_event_lookup( struct ati_remote_tbl *key_tbl, int rem, unsigned char d1, unsigned char d2)
That should do it. Let me know if there's still a problem.
-- ~Randy
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
