Serkan,
I think the best approach for what you have is to write the code
directly in user space. They are two reasons for this:
- They are already UART and I2C drivers for DM355 implemented that
will handle the data transmission, and those can be easily accessed
from user space (just call open() over /dev/ttySX and /dev/i2c-0 ?).
- Implementing a kernel driver may be overkiller and more difficult to
maintain.
I think implementing it over i2c could be hard; the DM355 is an i2c
master and I don't recall if it can run as slave. On the case is just
a master you will need a process or driver constantly polling the
second MCU, which could be inefficient. I would say UART sounds like a
better option.
You can open the UART port directly from your QT app and just receive
the information there.
Regards,
Diego Dompe
RidgeRun Engineering
On Feb 10, 2008, at 2:34 PM, serkan erdogan wrote:
Hii all,
i am developing the driver background for an qtopia application
running
on my DVEVM (dm355). My second embedded processor like TMS430 or any
equvalent processor will make all the required analog circuit and
time-sensitive jobs and will communicate wiht my DM355 via uart or i2c
in the device organization. This application doesn't have any standart
keyboard only have matrix type organized buttons and second mcu will
read the pressed button information and send to DM355 via a serial
protocol and inerface. Simultaneously, may be come some information
from
the second processor which is not about keyborad or any character
input
device. So a kernel modue must analyse the information each time it
comes.
The problem is that i dont know the best way for perform that. The
possiblities in my head are not much and i am confised a little;
1- Writing a kernel module which will analyse the all data coming to
UART and for a sanal keyboard than has node such as /dev/ttySX (i know
qtopia has support for tty keyboard drivers). But now one more
emulation
of concole is required for command enterance to linux.
2- Same as the first item but implemented on i2c bus.
3- A way for reading serial or i2c line from user-space directly and
there no need for driver.
4- The way that i wiss you tell me which is more efficent or easy.
As a summary i need thw best way for creating a standard character
input
driver from a nonstandard input device in linux.
I am sure there is some fault in my opinions above please please
correct
me at least. If you done it before please just say the best way. I
will
do my best for researcing and performing it.
Thank for reading and valuable help.
Serkan Erdoğan.
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
