From haas at ems-wuensche.com Wed Apr 8 08:50:30 2009 From: haas at ems-wuensche.com (Sebastian Haas) Date: Wed, 08 Apr 2009 10:50:30 +0200 Subject: CAN/USB Interface Socket-CAN Message-ID: <49DC6556.30604@ems-wuensche.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Project-Managers, we offer a wide range of CAN PC Interfaces and would love to see our products being supported out of the box of the mainline kernel. First some words about CAN. CAN (Controller Area Network) is fieldbus for industrial communication. Since 2.6.25 the Socket-CAN project got merged into the mainline kernel (drivers/net/can), it provides a generic API to access CAN PC Interfaces (PCI boards, USB, ISA, ...). See also http://developer.berlios.de/projects/socketcan/ We already provide GPLv2 Linux drivers to our customers but these drivers use a proprietary character device interface and are far away from getting merged into the kernel. In the past we have worked together with the Socket-CAN project to support our PCI interface (CPC-PCI) and PCMCIA interface (CPC-CARD). We have 2 products left which must be supported, one of it is the CPC-104M a PC-104 CAN interfaces and the other one is the CPC-USB a USB 1.1 CAN interface. The CPC-104M is a pretty simple device (memory mapped access to the CAN controller), which we will support in Socket-CAN ourself. The CPC-USB is a bit more trickier. What needs to be done: - - porting existing driver to Socket-CAN API - - implement power management We provide a test device and I will be the technical contact person (I've wrote our Linux driver before). Thank you very much. - -- Mit freundlichen Gruessen/Best Regards, Sebastian Haas Software Entwicklung/Software Development Phone: +49-9451-9432-22 Fax : +49-9451-9432-12 Email: haas at ems-wuensche.com Web : www.ems-wuensche.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkncZVQACgkQpqRB8PJG7Xz+uQCfXiPKAhH784jQ8F3ems/XXTOU r18AoIKUlofyc2fl1562H3UINJGlYWGc =bZyx -----END PGP SIGNATURE----- -- EMS Dr. Thomas Wuensche e.K. Sonnenhang 3 85304 Ilmmuenster HRA Neuburg a.d. Donau, HR-Nr. 70.106 Phone: +49-8441-490260 Fax : +49-8441-81860 http://www.ems-wuensche.com From phil at csldevices.co.uk Wed Apr 8 16:05:43 2009 From: phil at csldevices.co.uk (phil) Date: Wed, 08 Apr 2009 17:05:43 +0100 Subject: dvb-t reciever card Message-ID: <49DCCB57.4090903@csldevices.co.uk> Hi, I work for a company that is currently developing a new DVB-T receiver PCI card and we would like your help to get a Linux device driver written and into the mainline kernel. We plan to release our products specifications when launched, but until then we do require that an NDA is signed by anyone that would be willing to help out. I have briefly looked through some of the past archives of this list and I see that there has been some reference to NDAs from the Linux Foundation, we would be more than happy with using one of these and would appreciate it if someone could provide us with more information on them. Due to the fact that this is a DVB-T card any developer wishing to help should ideally be located in a country which has DVB-T broadcast signals in order to test any equipment which we supply. Please copy me in on any reponses as I believe I'm still awaiting authorisation to be subscribed to this list. Regards, Philip Downer From greg at kroah.com Mon Apr 13 15:46:28 2009 From: greg at kroah.com (Greg KH) Date: Mon, 13 Apr 2009 08:46:28 -0700 Subject: CAN/USB Interface Socket-CAN In-Reply-To: <49DC6556.30604@ems-wuensche.com> References: <49DC6556.30604@ems-wuensche.com> Message-ID: <20090413154628.GA31490@kroah.com> On Wed, Apr 08, 2009 at 10:50:30AM +0200, Sebastian Haas wrote: > Dear Project-Managers, > > we offer a wide range of CAN PC Interfaces and would love to see our > products being supported out of the box of the mainline kernel. > > First some words about CAN. CAN (Controller Area Network) is fieldbus for > industrial communication. Since 2.6.25 the Socket-CAN project got merged > into the mainline kernel (drivers/net/can), it provides a generic API to > access CAN PC Interfaces (PCI boards, USB, ISA, ...). > > See also http://developer.berlios.de/projects/socketcan/ > > We already provide GPLv2 Linux drivers to our customers but these drivers > use a proprietary character device interface and are far away from getting > merged into the kernel. Do you have a pointer to these drivers anywhere? If we convert them to use the proper in-kernel api, do you see a problem with them being merged? > In the past we have worked together with the Socket-CAN project to support > our PCI interface (CPC-PCI) and PCMCIA interface (CPC-CARD). > > We have 2 products left which must be supported, one of it is the CPC-104M > a PC-104 CAN interfaces and the other one is the CPC-USB a USB 1.1 CAN > interface. The CPC-104M is a pretty simple device (memory mapped access to > the CAN controller), which we will support in Socket-CAN ourself. > > The CPC-USB is a bit more trickier. Why do you think it is trickier? > What needs to be done: > - porting existing driver to Socket-CAN API > - implement power management Sounds very reasonable, and doable. > We provide a test device and I will be the technical contact person (I've > wrote our Linux driver before). Great! So, how do you want to do this? I suggest: - point us at the current drivers and we add them to the staging tree - work on converting them to the socket-can api - test with the devices provided all along the way Would that be acceptable? thanks, greg k-h From brandon at ifup.org Mon Apr 13 22:36:46 2009 From: brandon at ifup.org (Brandon Philips) Date: Mon, 13 Apr 2009 15:36:46 -0700 Subject: dvb-t reciever card In-Reply-To: <49DCCB57.4090903@csldevices.co.uk> References: <49DCCB57.4090903@csldevices.co.uk> Message-ID: <20090413223646.GB9763@jenkins.ifup.org> On 17:05 Wed 08 Apr 2009, phil wrote: > I work for a company that is currently developing a new DVB-T receiver > PCI card and we would like your help to get a Linux device driver > written and into the mainline kernel. The people with DVB-T expertise are on the linux-media at vger.kernel.org mailing list. CC'ing them to see if anyone is interested in working through the NDA process and writing the driver. Cheers, Brandon > We plan to release our products specifications when launched, but until > then we do require that an NDA is signed by anyone that would be willing > to help out. I have briefly looked through some of the past archives of > this list and I see that there has been some reference to NDAs from the > Linux Foundation, we would be more than happy with using one of these > and would appreciate it if someone could provide us with more > information on them. > > Due to the fact that this is a DVB-T card any developer wishing to help > should ideally be located in a country which has DVB-T broadcast signals > in order to test any equipment which we supply. > > Please copy me in on any reponses as I believe I'm still awaiting > authorisation to be subscribed to this list. From greg at kroah.com Thu Apr 16 02:59:21 2009 From: greg at kroah.com (Greg KH) Date: Wed, 15 Apr 2009 19:59:21 -0700 Subject: CAN/USB Interface Socket-CAN In-Reply-To: <49E43EDA.9080905@ems-wuensche.com> References: <49DC6556.30604@ems-wuensche.com> <20090413154628.GA31490@kroah.com> <49E43EDA.9080905@ems-wuensche.com> Message-ID: <20090416025921.GG4806@kroah.com> On Tue, Apr 14, 2009 at 09:44:26AM +0200, Sebastian Haas wrote: > Greg KH wrote: > > On Wed, Apr 08, 2009 at 10:50:30AM +0200, Sebastian Haas wrote: > >> Dear Project-Managers, > >> > >> we offer a wide range of CAN PC Interfaces and would love to see our > >> products being supported out of the box of the mainline kernel. > >> > >> First some words about CAN. CAN (Controller Area Network) is fieldbus for > >> industrial communication. Since 2.6.25 the Socket-CAN project got merged > >> into the mainline kernel (drivers/net/can), it provides a generic API to > >> access CAN PC Interfaces (PCI boards, USB, ISA, ...). > >> > >> See also http://developer.berlios.de/projects/socketcan/ > >> > >> We already provide GPLv2 Linux drivers to our customers but these drivers > >> use a proprietary character device interface and are far away from getting > >> merged into the kernel. > > > > Do you have a pointer to these drivers anywhere? If we convert them to > > use the proper in-kernel api, do you see a problem with them being > > merged? > No. They don't use any exotic constructions nor binary blobs. I've already > tried to fix some coding style issues. There are some #IFDEFs to > support older kernels and they don't make use of modern USB and driver > functions (USB anchors or dev_info(...)) also with respect to older kernels. That's not a problem, we can clean them up quite easily in the staging tree. > >> In the past we have worked together with the Socket-CAN project to support > >> our PCI interface (CPC-PCI) and PCMCIA interface (CPC-CARD). > >> > >> We have 2 products left which must be supported, one of it is the CPC-104M > >> a PC-104 CAN interfaces and the other one is the CPC-USB a USB 1.1 CAN > >> interface. The CPC-104M is a pretty simple device (memory mapped access to > >> the CAN controller), which we will support in Socket-CAN ourself. > >> > >> The CPC-USB is a bit more trickier. > > > > Why do you think it is trickier? > Socket-CAN already has support for the onboard CAN controllers at our PCI > boards. So supporting them is just a matter of 300lines of simple code. Great! Although 300 lines of code does seem like a lot, we can write a virtual filesystem for Linux in less these days :) > In our proprietary API, most configuration stuff comes from the > application which uses the CPC-USB device. Socket-CAN does it all in > kernel space as it provides a single device to many applications > (networking like). So the configuration process and some specific > processing needs to be moved to kernel space (nothing exciting but just > more work). > > >> What needs to be done: > >> - porting existing driver to Socket-CAN API > >> - implement power management > > > > Sounds very reasonable, and doable. > > > >> We provide a test device and I will be the technical contact person (I've > >> wrote our Linux driver before). > > > > Great! > > > > So, how do you want to do this? I suggest: > > - point us at the current drivers and we add them to the > > staging tree > > - work on converting them to the socket-can api > > - test with the devices provided all along the way > > > > Would that be acceptable? > Yes, sounds great. Give me some days to prepare everything. > > Who will be the responsible developer at the Linux driver project? I'll start it out, as you already have code, and then other developers will pick it up and go from there. Send me the code you have when you are ready to start. thanks, greg k-h From phil at csldevices.co.uk Tue Apr 21 14:23:30 2009 From: phil at csldevices.co.uk (phil) Date: Tue, 21 Apr 2009 15:23:30 +0100 Subject: dvb-t reciever card In-Reply-To: <20090413223646.GB9763@jenkins.ifup.org> References: <49DCCB57.4090903@csldevices.co.uk> <20090413223646.GB9763@jenkins.ifup.org> Message-ID: <49EDD6E2.2020501@csldevices.co.uk> Brandon Philips wrote: > On 17:05 Wed 08 Apr 2009, phil wrote: > >> I work for a company that is currently developing a new DVB-T receiver >> PCI card and we would like your help to get a Linux device driver >> written and into the mainline kernel. >> > > The people with DVB-T expertise are on the linux-media at vger.kernel.org > mailing list. CC'ing them to see if anyone is interested in working > through the NDA process and writing the driver. > Thanks for the quick response and for forwarding my mail onwards but given that theres been no response on the linux-media list what is the best way for us to continue with this? Regards, Philip Downer From haas at ems-wuensche.com Tue Apr 14 07:44:37 2009 From: haas at ems-wuensche.com (Sebastian Haas) Date: Tue, 14 Apr 2009 07:44:37 -0000 Subject: CAN/USB Interface Socket-CAN In-Reply-To: <20090413154628.GA31490@kroah.com> References: <49DC6556.30604@ems-wuensche.com> <20090413154628.GA31490@kroah.com> Message-ID: <49E43EDA.9080905@ems-wuensche.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg KH wrote: > On Wed, Apr 08, 2009 at 10:50:30AM +0200, Sebastian Haas wrote: >> Dear Project-Managers, >> >> we offer a wide range of CAN PC Interfaces and would love to see our >> products being supported out of the box of the mainline kernel. >> >> First some words about CAN. CAN (Controller Area Network) is fieldbus for >> industrial communication. Since 2.6.25 the Socket-CAN project got merged >> into the mainline kernel (drivers/net/can), it provides a generic API to >> access CAN PC Interfaces (PCI boards, USB, ISA, ...). >> >> See also http://developer.berlios.de/projects/socketcan/ >> >> We already provide GPLv2 Linux drivers to our customers but these drivers >> use a proprietary character device interface and are far away from getting >> merged into the kernel. > > Do you have a pointer to these drivers anywhere? If we convert them to > use the proper in-kernel api, do you see a problem with them being > merged? No. They don't use any exotic constructions nor binary blobs. I've already tried to fix some coding style issues. There are some #IFDEFs to support older kernels and they don't make use of modern USB and driver functions (USB anchors or dev_info(...)) also with respect to older kernels. >> In the past we have worked together with the Socket-CAN project to support >> our PCI interface (CPC-PCI) and PCMCIA interface (CPC-CARD). >> >> We have 2 products left which must be supported, one of it is the CPC-104M >> a PC-104 CAN interfaces and the other one is the CPC-USB a USB 1.1 CAN >> interface. The CPC-104M is a pretty simple device (memory mapped access to >> the CAN controller), which we will support in Socket-CAN ourself. >> >> The CPC-USB is a bit more trickier. > > Why do you think it is trickier? Socket-CAN already has support for the onboard CAN controllers at our PCI boards. So supporting them is just a matter of 300lines of simple code. In our proprietary API, most configuration stuff comes from the application which uses the CPC-USB device. Socket-CAN does it all in kernel space as it provides a single device to many applications (networking like). So the configuration process and some specific processing needs to be moved to kernel space (nothing exciting but just more work). >> What needs to be done: >> - porting existing driver to Socket-CAN API >> - implement power management > > Sounds very reasonable, and doable. > >> We provide a test device and I will be the technical contact person (I've >> wrote our Linux driver before). > > Great! > > So, how do you want to do this? I suggest: > - point us at the current drivers and we add them to the > staging tree > - work on converting them to the socket-can api > - test with the devices provided all along the way > > Would that be acceptable? Yes, sounds great. Give me some days to prepare everything. Who will be the responsible developer at the Linux driver project? > thanks, > > greg k-h Thank you too. - -- Mit freundlichen Gruessen/Best Regards, Sebastian Haas Software Entwicklung/Software Development Phone: +49-9451-9432-22 Fax : +49-9451-9432-12 Email: haas at ems-wuensche.com Web : www.ems-wuensche.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknkPtQACgkQpqRB8PJG7XxboQCghUmWpcuOlQ5fcK+2LEBzRmLK MQkAmQEHi1/seHpEmkXt8lurjbUvTP4O =cQ/L -----END PGP SIGNATURE----- -- EMS Dr. Thomas Wuensche e.K. Sonnenhang 3 85304 Ilmmuenster HRA Neuburg a.d. Donau, HR-Nr. 70.106 Phone: +49-8441-490260 Fax : +49-8441-81860 http://www.ems-wuensche.com