Wanted: Serial_cs.o For C3000/linux 2.4.20, Sharp's version shows Bad Vcc in dmesg Options

[dhns]

I think that all the patches Tetsu included in his kernel are available from the same page, you should be able to patch the stock Sharp kernel and recompile it, making the serial stuff a module.

I have tried to find my way through the translation of his page (having two Safari windows open - one with translation, original the other :-).
I found an .ipk (SL-C1000/C3000 kernel modules (v18a))for additional kernel modules (e.g. Bluetooth) for the C3000 but it does contain only the directory ./lib/modules/2.4.20/pcmcia/ but no patch. So, he must have patched that to the kernel, but I can't find.

-- hns

[Ping]

Hello!

I remember I had problems with GPS CF when I developed a software for Zaurus

I have cross-compiled the serial_cs.o from the Linux kernel 2.4.29 and it works!

I have done a memo for this

I have test on a Zaurus SL-C760 but I will try to see if it works on a my Zaurus SL-C3100

(sorry for my english, I'm french!)

[dhns]

I cross-compile the serial_cs.o from the Linux kernel 2.4.29  and it works!
I have test on a Zaurus SL-C760 but I will try to see if it works on a my Zaurus SL-C3100

That would be great! I already have a working serial_cs.o for the C7x0/860 models (Kernel 2.4.18) but couldn't find any one for the C3000/3100 models with 2.4.20 kernel.

-- hns

[euroclie]

I have tried to find my way through the translation of his page (having two Safari windows open - one with translation, original the other :-).
I found an .ipk (SL-C1000/C3000 kernel modules (v18a))for additional kernel modules (e.g. Bluetooth) for the C3000 but it does contain only  the directory ./lib/modules/2.4.20/pcmcia/ but no patch. So, he must have patched that to the kernel, but I can't find.

Use the following link:

http://translate.google.com/translate?hl=e...hl%3Den%26lr%3D

And look for the part shown in the attached picture
 tetsu3k.jpg ( 113.86K ) Number of downloads: 28


All the patches are available as text files from the main page (P01, P02, etc.) so it shouldn't be too hard to get them, apply them to the stock 3000 kernel sources and recompile it with serial as a module...

Happy compiling!

[Ping]

Try this

don't forget to run "cardctl resume 0 "

I see when I cross-compile my kernel that serial_cs is not compiled as module so you should cross-compile your own kernel and disable serial_cs than copy my serial_cs.o to /lib/modules/2.4.20/kernel/drivers/pcmcia (on the Zaurus)

Attached File(s)

 serial_cs.o.tar.gz ( 4.05K ) Number of downloads: 37

 

[dhns]

I have tried to find my way through the translation of his page (having two Safari windows open - one with translation, original the other :-).
I found an .ipk (SL-C1000/C3000 kernel modules (v18a))for additional kernel modules (e.g. Bluetooth) for the C3000 but it does contain only  the directory ./lib/modules/2.4.20/pcmcia/ but no patch. So, he must have patched that to the kernel, but I can't find.

Use the following link:

http://translate.google.com/translate?hl=e...hl%3Den%26lr%3D

And look for the part shown in the attached picture
 tetsu3k.jpg ( 113.86K ) Number of downloads: 28


All the patches are available as text files from the main page (P01, P02, etc.) so it shouldn't be too hard to get them, apply them to the stock 3000 kernel sources and recompile it with serial as a module...

Happy compiling!

I already had translated that - but which one modifies the serial_cs for PCMCIA? If I want to just patch that, I can't apply any other patch to the kernel...

-- hns

[dhns]

Try this

Great!

This seems to work on the C3000! I just got the first ATI response!

Just wondering why there are so many kernels out there when installing a module is sufficient...

-- hns

[maslovsky]

So, te buttomline is to use the module from 2.4.29 kernel? What about Sharp patches? Does it work fine with stock modules without them?

[euroclie]

I already had translated that - but which one modifies the serial_cs for PCMCIA? If I want to just patch that, I can't apply any other patch to the kernel...

Look in the (P11) bluetooth-mh18_041216 patch, it seems that the serial_cs file gets patched in there (didn't have an extensive look, it's just that at line #5644 you find this:

CODE

diff -Nur c3000_pre/linux/drivers/char/pcmcia/serial_cs.c c3000_work/linux/drivers/char/pcmcia/serial_cs.c
--- c3000_pre/linux/drivers/char/pcmcia/serial_cs.c    2004-08-21 09:48:33.000000000 +0900
+++ c3000_work/linux/drivers/char/pcmcia/serial_cs.c    2004-12-16 23:01:14.000000000 +0900
@@ -2,7 +2,7 @@

    A driver for PCMCIA serial devices

-    serial_cs.c 1.128 2001/10/18 12:18:35
+    serial_cs.c 1.138 2002/10/25 06:24:52

I'll leave it up to you to check if there's anything usefull for you in there (as for me, there isn't much I can make sense of, my C knowledge being very limited)!

[euroclie]

Just wondering why there are so many kernels out there when installing a module is sufficient...

As far as I could make out from the Japanese stuff, Tetsu's kernel contains a lot of bug fixes and improvements that make it a valuable choice, and which couldn't necessarily be implemented as standalone modules... but then I may be wrong, I'm not a kernel guru.

[maslovsky]

Actualy I didn't see any difference between 2.4.21 and 2.4.31 versions of the serial_cs code. Maybe "cardctl resume 0" comamnd was the key?

[euroclie]

Actualy I didn't see any difference between 2.4.21 and 2.4.31 versions of the serial_cs code.  Maybe "cardctl resume 0" comamnd was the key?

I remember that I had troubles with my Audiovox-compatible card at the beginning. It wouldn't work at all, until I indeed issued that "cardctl resume 0" command (the key on the 3000 is to append the slot number to the resume command, as there are two slots unlike the older devices).

Then I was able to play with the card using minicom, and proceed to other things like getting PPP to work with it. That's when I discovered that I needed to resume the card for minicom to see it, but if it was resumed I coudln't use it with the GUI to connect to the net (using PPP), which required it to be suspended first. Go figure!

Right now I seem to have somehow damaged the card when transporting it along with my Zaurus, as I can't stay connected for more than 30 seconds or so, and I've (temporarily at least) put it aside while I have serious work to do... I'll play again with it in a few weeks/months.

[dhns]

Actualy I didn't see any difference between 2.4.21 and 2.4.31 versions of the serial_cs code.  Maybe "cardctl resume 0" comamnd was the key?

Hm,
the two serial_cs.o files posted here differ in file length by 4 bytes. And the second one works (at least for my C3000 + Audiovox RTM 8000).
No Idea why.

-- hns

[Ping]

Actualy I didn't see any difference between 2.4.21 and 2.4.31 versions of the serial_cs code.  Maybe "cardctl resume 0" comamnd was the key?

Hm,
the two serial_cs.o files posted here differ in file length by 4 bytes. And the second one works (at least for my C3000 + Audiovox RTM 8000).
No Idea why.

-- hns

Maybe the compiler. I used gcc-2.95.4

[dhns]

Maybe the compiler. I used gcc-2.95.4

Or some other kernel configuration which includes one more statement?

-- hns