Porting the device drivers ARM->x86 ; Vxworks->Linux

Porting the device drivers ARM->x86 ; Vxworks->Linux

Post by Rush » Wed, 13 Oct 2004 18:00:20

Porting the device drivers.

We are using SCC2691 UART for extra serial port on our custom x86
board. We already have Vxworks drivers aviable for this device. We
have moved to Embedded Linux recently.

Luckily can't find any SCC2691 driver for x86 any were on the net (Any
I found some support for this device for ARM based custom hardware
from coral.

I have the scc2691.c file from ARM driver now, and from the patch
where i got the driver i can see what changes i need to make to
tty_o.c , Makefile,Config.in.

Now I am going to add scc2691.c in my /drivers/char/ kernel tree and
modifying the Makefile, tty_o.c and Config.in files. We don't have any
moulder support for the kernel so i am compiling the drives with no
module support in kernel.

First if the kernel compiles withouts any errors What possibilities
are there for ARM driver to work on X86 ???

Does my method to adding the driver in kernel source need any thing
else ???

Any kind of guidance is appreciated.




Porting the device drivers ARM->x86 ; Vxworks->Linux

Post by RusH » Thu, 14 Oct 2004 16:58:57

Quote:> I have the scc2691.c
> Any kind of guidance is appreciated.

you can ask those guys http://www.tern.com/586e_data.htm
but after quick look it looks like its memory mapped uard, just make
sure the ports match and it schould be fine.

RusH   //
Like ninjas, true hackers are shrouded in secrecy and mystery.
You may never know -- UNTIL IT'S TOO LATE.


1. touch-screen device<->device driver<-xinput extension-><-X client interaction?

Hi, There,

Could someone take a break for a minute, feel himself a
professor and
give me (and, possibly others interesting fellows) a short

Our in-house made pc486 touch-screen controller is attached to a
port and uses IRQ7 to notify CPU about "touch".

It will be used as input device for X windows system. The
problem is I'm UNIX
illiterate so don't have clear understanding how all these
pieces (touch-screen
controller, touch-screen device driver, kernel, touch-screen
Xinput extension,
X server, X client) communicate to each other. So far I
understood that, for example,
standard Elographics touch-screen controller (connected to
/dev/ttyS1) is actually
controlled by serial port driver, and xf86Elo.so xinput
extension is interfacing between
X server and serial driver (am I right so far?). So to get this
thing working I would have to
write parallel port device driver-IRQ7 handler, create new
special device file, say /dev/touch
pointing to entry points from device driver, somehow let kernel
know there's new driver,
somehow update relevant (what?) kernel's structures so they will
actually point to driver's entry
point according to major/minor of /dev/touch, edit xf86Elo.c to
be able to use it with our
simplified controller. Is it sounds close to the truth? If not,
could somebody tell me how
those pieces work together, pleeeese?


Pavel Tkatchouk

2. Question about the SCO5 Virtual disk subsystem (for mirroring)


4. SBus-based drivers (32-bit vs 64-bit Solais Kernels)

5. Wanted: <><><> Unix Specialist <><><>

6. PeterColonMan

7. LILO help <><><><><><>

8. relative "busyness" of machines

9. >>---> Software Jobs! >>--->

10. FTP problem: linux>>win/SGI slow win/SGI>>linux fast

11. linux IMAP ->NE2000->ncsa packet driver->PC_PINE???

12. Win95/IPX -> IP ->PPP ->Linux ->Novell 3.12