From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Mon, 26 Oct 2009 07:26:58 -0400 Subject: [U-Boot] CAN console In-Reply-To: <4AE5834F.5040307@arcor.de> References: <4AE55BB2.6090608@arcor.de> <200910260437.32577.vapier@gentoo.org> <4AE5834F.5040307@arcor.de> Message-ID: <200910260726.59949.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Monday 26 October 2009 07:09:03 Matthias Wei?er wrote: > Mike Frysinger schrieb: > > On Monday 26 October 2009 04:20:02 Matthias Wei?er wrote: > >> I have a device here which has only a CAN interface to the > >> outside world. I am currently thinking about implementing > >> a "serial" driver using the CAN controller. > >> > >> Is there any chance to get this accepted in the public u-boot > >> tree? > > > > someone just posted a port of the Linux CAN framework. if your driver > > used that to implement a serial layer, i dont see why it wouldnt be > > accepted. > > Well, that means that I have to implement a full functional CAN driver > and then additionally add a serial driver using the (completely new) CAN > framework. My idea was that I just add a serial_ccan.c to drivers/serial. you would rather write a driver that is specific to one CAN hardware ? writing it to a common framework would allow every one with a CAN driver to use it ... -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20091026/bc264a6d/attachment.pgp