David Campbell (campbell@torque.net)
Tue, 16 Mar 1999 11:32:49 +0800
From: Carlos Henrique Bauer <chbauer@acm.org>
Send reply to: chbauer@acm.org
To: linux-parport@torque.net
Subject: [PARPORT] unresolved symbol in parport
Date sent: Mon, 15 Mar 1999 23:45:59 -0300
> Hi,
>
> I installed linux 2.2.3 and the tmw4 parport patch. When I try to insert the
> parport module I get the message:
>
> ./parport.o: unresolved symbol memset
I have seen this also with kernel modules, I believe that you will
find that memset is not used in any of the code!?!
I have seen this with the ppa/imm drivers where if a local
array/structure is initialised at declaration to zero, the compiler
(gcc/egcs) will insert "memset(<variable>,0,sizeof(<variable>))". The
only solution is to declare the variable and then fill the array by
hand.
Anyway, that is a reason but not the solution to problem.
eg:
=========================
foobar()
{
/* This breaks kernel modules */
unsigned char cmd[6] = {0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
}
nofoobar()
{
/* This is OK */
unsigned char cmd[6];
cmd[0] = 0x00, cmd[1] = 0x00, cmd[2] = 0x00;
cmd[3] = 0x00, cmd[4] = 0x00, cmd[5] = 0x00;
}
=========================
David Campbell
=======================================================
campbell@torque.net
Check http://www.torque.net/parport for all Linux parallel port solutions.
(also check http://www.torque.net/parport/archive/current/)
Current project list:
a) Catch up on the ZIP Plus backlog (drive back from waranty)
b) Maintain Linux ZIP drivers (need to update docs)
c) sleep
d) real life
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Sun 28 Mar 1999 - 17:00:20 EST