Re: adding can4linux to drivers/char

["Heinz-Jürgen Oertel" <hj.oertel@t-online.de>]

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]


Hello

Am Samstag, 21. September 2013, 21:55:45 schrieb Wolfgang Grandegger:
> I think you need *strong* arguments to get it accepted. 

I have some good arguments for this kind of driver
- it is much more simple in design than others,
  simplicity is one of the Linux design goals
- It has a simple user API
- It does not need any other infrastructure than the kernel API
- It is mature

I agree, it would be nice to share the low level CAN controller related 
experiences of the developers. That is may be something we can share if we 
could agree of a set of CAN controller header files with shared register 
#defines. And a set of very basic functions like initialize and activate CAN, 
set acceptance filters, transmit and receive, read out error register or 
whatever.
But to stay simple, I don't like the idea to have another additional layer 
around SocketCAN as layer below the can4linux API.

Linux offers real diversity on the desktop, why not with drivers? Linux also 
has different sound devices and architectures.  Why not offering two different 
CAN driver concepts to the application programmer,
let she decide what to use.

-- 
mit freundlichen Grüßen
       Heinz-Jürgen Oertel

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]