Re: [microblaze-uclinux] Howto access FSL with uClinux?

[Christian Schleiffer <christian.schleiffer@xxxxxxxxxxxxxxxxxx>]

Hi folks,

I finally got my code compiled and almost everything seems to work
except for a missing device entry. The FSL FIFO Driver is activated:

> Microblaze FSL FIFO Driver. John Williams <jwilliams@xxxxxxxxxxxxxx>
> FSL FIFO[1] initialised

but when I try to create a device node, I get an error message because
/dev/ is read only.

> mknod: fslfifo1: Read-only file system

In [1] John wrote
> As for dynamic, I guess the problem is that most uClinux targets mount 
> the root FS as read only, so running mknod in /dev is not usually 
> possible.  In my local vendors Makefile I added the fslfifo devs 
> statically...

But I'm not sure, how this is actually done... I can't find any hints in
the uclinux-dist directory. Ideas, anybody?

Cheers
/Chris


[1]
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2004/11/msg00008.html

-------- Original Message  --------
Subject: Re:[microblaze-uclinux] Howto access FSL with uClinux?
From: Claudio Lanconelli <lanconelli.claudio@xxxxxxxxx>
To: microblaze-uclinux@xxxxxxxxxxxxxx
Cc: christian.schleiffer@xxxxxxxxxxxxxxxxxx
Date: Tue Dec 19 2006 13:07:43 GMT+0100

> Hi Christian,
> look at this message for basic example on using flsfifo
> 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2005/10/msg00167.html
> 
> Cheers,
> Claudio Lanconelli
> 
> Christian Schleiffer wrote:
>> Hi List,
>>
>> I need to access an FSL port with my own hardware attached, but I'm not
>> sure how to do it correctly. I found the FSL driver by John but don't
>> know how to use it correctly.  fslfifo.c says:
>>
>>   
>>> [...]
>>> * Simple driver to provide Linux-style FIFO interface to custom hardware
>>> * peripherals connected to Microblaze FSL ports.  See Microblaze user manual
>>> * for details of FSL architecture.
>>> *
>>> * read() and write() operate on software buffers, with a tasklet scheduled
>>> * to actually stuff data into / out of FSL ports.  This might be better 
>>> * served by interrupts, however the hardware doesn't support it yet.
>>> [...]
>>>     
>>
>> So I guess, it works quite similar to usual file handling? Can anybody
>> give me with a short example or a link? I was not able to find any code
>> or documentation on the net (except for the Xilinx stuff only mentioning
>> low-level blocking access).
>>
>> Thanks in advance
>> Cheers
>> /Chris
>> ___________________________
>> microblaze-uclinux mailing list
>> microblaze-uclinux@xxxxxxxxxxxxxx
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>
>>
>>   
> 
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/