mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Parallel port misbehavior using kernel 2.4.19 and pcchips M810
@ 2002-11-08 12:38 Fernando Fraga e Silva
  2002-11-07 16:19 ` Richard B. Johnson
  0 siblings, 1 reply; 3+ messages in thread
From: Fernando Fraga e Silva @ 2002-11-08 12:38 UTC (permalink / raw)
  To: linux-kernel

Hi Guys
I'm working for 4 days on a parallel port misbehavior problem without having 
any sucess. I have to control a device with SPP mode using a pcchips M810, a 
Duron processor and a kernel 2.4.19.
So I made the following simple code :
--
#include <asm/io.h> //i've tried <sys/io.h>  too
int main ()
{
ioperm( 0x378, 3, 1);
outb (0x01, 0x378 );
ioperm (0x378, 3, 0);
return 0;
}
--
And copiled with "gcc -O2 test.c -o test; ./test".  running it as superuser 
the result should be a "1" logic on pin "2" of parallel port.
Ok it is correct except for this motherboard, it works on Soyo+K6 , 
Gigabyte+Athlon, i810+Celeron, etc. But it doesn't for M810+Duron.
I verified the BIOS setup, changed the kernel source for 2.2.20, changed the 
motherboard for M812, recompiled and recompiled the kernel, changed the 
distro from Debian/Woody to Debian/Testing. None of this worked.

So I tried to install Win95 and make it using a assembler code ... It worked.

The next thing i've done was start making a kernel module.... it worked for 
Gigabyte+Athlon, i810+Celeron, Soyo+K6 and a old PC-Chips board with K6 
processor....but nothing happened for the M810+Duron board though.

So I thought it should be a problem with outb call, so I made a module using 
assembler instead outb call, it was compiled with success and was installed. 
The requested i/o region was reserved with success but didn't work with 
M810+Duron. Though It worked with Gigabyte+Athlon and Soyo+K6 again.
So i get the old code (as i listed above)  and after testing it with success 
again in the Soyo+K6 board i compiled it and linked the program statically. i 
brought the executable to the M810+Duron and it didn't work again... though 
it always runs without any errors the signals are not present on the parallel 
port. 

I tried to access the parallel port through /dev/ports using lseek to get the 
0x378 address position... and the result was the same... nothing for 
M810+Duron

I don't know any more to do, and I'm wondered if anyone here can help me. I 
can't believe it will not work on this motherboard if the parallel works 
perfectly. If anyone have any information about this parallel port on this 
motherboard, any code or any related knowlegment and like to share It would 
be a lot appreciated.

Thanks.

Fernando.


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Parallel port misbehavior using kernel 2.4.19 and pcchips M810
@ 2002-11-08  9:12 Fernando Fraga e Silva
  0 siblings, 0 replies; 3+ messages in thread
From: Fernando Fraga e Silva @ 2002-11-08  9:12 UTC (permalink / raw)
  To: linux-kernel; +Cc: thiago

Hi Guys

I'm working for 4 days on a parallel port misbehavior problem without having 
any sucess. I have to control a device with SPP mode using a pcchips M810, a 
Duron processor and a kernel 2.4.19.

So I made the following simple code :
--
#include <asm/io.h> //i've tried <sys/io.h>  too
int main ()
{
ioperm( 0x378, 3, 1);
outb (0x01, 0x378 );
ioperm (0x378, 3, 0);
return 0;
}
--
And copiled with "gcc -O2 test.c -o test; ./test".  running it as superuser 
the result should be a "1" logic on pin "2" of parallel port.
Ok it is correct except for this motherboard, it works on Soyo+K6, 
Gigabyte+Athlon, i810+Celeron, etc. But it doesn't for M810+Duron.
I verified the BIOS setup, changed the kernel source for 2.2.20, changed the 
motherboard for M812, recompiled and recompiled the kernel, changed the 
distro from Debian/Woody to Debian/Testing. None of this worked.

So I tried to install Win95 and make it using a assembler code ... It worked.

The next thing i've done was start making a kernel module.... it worked for 
Gigabyte+Athlon, i810+Celeron, Soyo+K6 and a old PC-Chips board with K6 
processor....but nothing happened for the M810+Duron board though.

So I thought it should be a problem with outb call, so I made a module using 
assembler instead outb call, it was compiled with success and was installed. 
The requested i/o region was reserved with success but didn't work with 
M810+Duron. Though It worked with Gigabyte+Athlon and Soyo+K6 again.
So i get the old code (as i listed above)  and after testing it with success 
again in the Soyo+K6 board i compiled it and linked the program statically. i 
brought the executable to the M810+Duron and it didn't work again... though 
it always runs without any errors the signals are not present on the parallel 
port.

I tried to access the parallel port through /dev/ports using lseek to get the 
0x378 address position... and the result was the same... nothing for 
M810+Duron

I don't know any more to do, and I'm wondered if anyone here can help me. I 
can't believe it will not work on this motherboard if the parallel works 
perfectly. If anyone have any information about this parallel port on this 
motherboard, any code or any related knowlegment and like to share It would 
be a lot appreciated.

Thanks.

Fernando.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-11-07 16:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-08 12:38 Parallel port misbehavior using kernel 2.4.19 and pcchips M810 Fernando Fraga e Silva
2002-11-07 16:19 ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2002-11-08  9:12 Fernando Fraga e Silva

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®