From mszanyi at zcomax.com Mon Dec 6 18:13:12 2010 From: mszanyi at zcomax.com (Mitch Szanyi) Date: Mon, 6 Dec 2010 13:13:12 -0500 Subject: FW: Request for driver development Message-ID: <002401cb9571$3f2da470$bd88ed50$@com> Please see the attached file for product table. From: Mitch Szanyi [mailto:mszanyi at zcomax.com] Sent: Monday, December 06, 2010 11:59 AM To: 'prjmgr at linuxdriverproject.org' Subject: Request for driver development Hi, My company Zcomax Technologies, Inc. is the acting business center in North America for the Radio manufacturer Zcom based in Taiwan. One of our customer's has pointed me to your direction in order to see if you would be willing to develop drivers for our products. I understand you will need some documentation which we can provided and an NDA will only be required if we have information that we need to protect but I do not see offhand where that will be necessary. Attached are the spec sheets for the products I have listed below in case you need any details. If you need more information at this time let me know and I will get back to you promptly and If this does look like something you are willing to undertake I will provide to you whatever information you may need. Best regards, Mitch Szanyi Zcomax Technologies, Inc. www.zcomax.com www.zcom.com.tw -------------- next part -------------- A non-text attachment was scrubbed... Name: Zcomax_Spec.7z Type: application/octet-stream Size: 822638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Request for driver development.7z Type: application/octet-stream Size: 4832 bytes Desc: not available URL: From mszanyi at gmail.com Mon Dec 6 18:21:27 2010 From: mszanyi at gmail.com (Mitch Szanyi) Date: Mon, 6 Dec 2010 13:21:27 -0500 Subject: FW: Request for driver development Message-ID: <000001cb9572$66bc54e0$3434fea0$@com> -----Original Message----- From: Mitch Szanyi [mailto:mszanyi at zcomax.com] Sent: Monday, December 06, 2010 1:13 PM To: 'prjmgr at linuxdriverproject.org' Subject: FW: Request for driver development Please see the attached file for product table. From: Mitch Szanyi [mailto:mszanyi at zcomax.com] Sent: Monday, December 06, 2010 11:59 AM To: 'prjmgr at linuxdriverproject.org' Subject: Request for driver development Hi, My company Zcomax Technologies, Inc. is the acting business center in North America for the Radio manufacturer Zcom based in Taiwan. One of our customer's has pointed me to your direction in order to see if you would be willing to develop drivers for our products. I understand you will need some documentation which we can provided and an NDA will only be required if we have information that we need to protect but I do not see offhand where that will be necessary. Attached are the spec sheets for the products I have listed below in case you need any details. If you need more information at this time let me know and I will get back to you promptly and If this does look like something you are willing to undertake I will provide to you whatever information you may need. Best regards, Mitch Szanyi Zcomax Technologies, Inc. www.zcomax.com www.zcom.com.tw -------------- next part -------------- A non-text attachment was scrubbed... Name: Zcomax_Spec.7z Type: application/octet-stream Size: 822638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Request for driver development.7z Type: application/octet-stream Size: 4832 bytes Desc: not available URL: From greg at kroah.com Mon Dec 6 19:56:24 2010 From: greg at kroah.com (Greg KH) Date: Mon, 6 Dec 2010 11:56:24 -0800 Subject: FW: Request for driver development In-Reply-To: <000001cb9572$66bc54e0$3434fea0$@com> References: <000001cb9572$66bc54e0$3434fea0$@com> Message-ID: <20101206195623.GA11981@kroah.com> On Mon, Dec 06, 2010 at 01:21:27PM -0500, Mitch Szanyi wrote: > Hi, > My company Zcomax Technologies, Inc. is the acting business center in North > America for the Radio manufacturer Zcom based in Taiwan. One of our > customer's has pointed me to your direction in order to see if you would be > willing to develop drivers for our products. I understand you will need some > documentation which we can provided and an NDA will only be required if we > have information that we need to protect but I do not see offhand where that > will be necessary. Attached are the spec sheets for the products I have > listed below in case you need any details. > > If you need more information at this time let me know and I will get back to > you promptly and If this does look like something you are willing to > undertake I will provide to you whatever information you may need. As all of these devices are based on Atheros chipsets, are you sure that Linux doesn't already support them today? What is the PCI and USB vendor/device ids of the different devices you are wishing to support? thanks, greg k-h From greg at kroah.com Mon Dec 6 21:22:41 2010 From: greg at kroah.com (Greg KH) Date: Mon, 6 Dec 2010 13:22:41 -0800 Subject: FW: Request for driver development In-Reply-To: <003101cb958a$acfdf0e0$06f9d2a0$@com> References: <000001cb9572$66bc54e0$3434fea0$@com> <20101206195623.GA11981@kroah.com> <003101cb958a$acfdf0e0$06f9d2a0$@com> Message-ID: <20101206212241.GA5519@kroah.com> On Mon, Dec 06, 2010 at 04:15:12PM -0500, Mitch Szanyi wrote: > Hi Greg, > > I will need to confirm what the ID's are as some use the Atheros default > while others are changed to our internal ID's. The non standard frequencies > may need some tweaking but I will also need to verify what specific chipsets > you already have drivers for and what ones you may not. Sure, just ask. Or better yet, you can try out a latest kernel from www.kernel.org and let us know which devices of yours do not work. > As I am new in regards to working with the opensource community, may I ask > if there is anything you may need from a company n our position as well? We > have many customers working with opensource drivers for our devices as well > as firmware packages and they are all pushing us to take a proactive > approach to assisting the community, this assisting them. For wireless drivers and devices like yours, it's best for you to work directly with the wireless developers. They can be found on the linux-wireless at vger.kernel.org mailing list. This is especially true as odds are, all you need is a few new device ids added to the existing drivers, something that would be very trivial for those developers to do. Hope this helps, greg k-h From mszanyi at gmail.com Mon Dec 6 21:15:12 2010 From: mszanyi at gmail.com (Mitch Szanyi) Date: Mon, 6 Dec 2010 16:15:12 -0500 Subject: FW: Request for driver development In-Reply-To: <20101206195623.GA11981@kroah.com> References: <000001cb9572$66bc54e0$3434fea0$@com> <20101206195623.GA11981@kroah.com> Message-ID: <003101cb958a$acfdf0e0$06f9d2a0$@com> Hi Greg, I will need to confirm what the ID's are as some use the Atheros default while others are changed to our internal ID's. The non standard frequencies may need some tweaking but I will also need to verify what specific chipsets you already have drivers for and what ones you may not. As I am new in regards to working with the opensource community, may I ask if there is anything you may need from a company n our position as well? We have many customers working with opensource drivers for our devices as well as firmware packages and they are all pushing us to take a proactive approach to assisting the community, this assisting them. Thank you -----Original Message----- From: Greg KH [mailto:greg at kroah.com] Sent: Monday, December 06, 2010 2:56 PM To: Mitch Szanyi Cc: prjmgr at linuxdriverproject.org Subject: Re: FW: Request for driver development On Mon, Dec 06, 2010 at 01:21:27PM -0500, Mitch Szanyi wrote: > Hi, > My company Zcomax Technologies, Inc. is the acting business center in North > America for the Radio manufacturer Zcom based in Taiwan. One of our > customer's has pointed me to your direction in order to see if you would be > willing to develop drivers for our products. I understand you will need some > documentation which we can provided and an NDA will only be required if we > have information that we need to protect but I do not see offhand where that > will be necessary. Attached are the spec sheets for the products I have > listed below in case you need any details. > > If you need more information at this time let me know and I will get back to > you promptly and If this does look like something you are willing to > undertake I will provide to you whatever information you may need. As all of these devices are based on Atheros chipsets, are you sure that Linux doesn't already support them today? What is the PCI and USB vendor/device ids of the different devices you are wishing to support? thanks, greg k-h From maciej.grela at gmail.com Mon Dec 6 21:39:40 2010 From: maciej.grela at gmail.com (Maciej Grela) Date: Mon, 6 Dec 2010 22:39:40 +0100 Subject: FW: Request for driver development In-Reply-To: <003101cb958a$acfdf0e0$06f9d2a0$@com> References: <000001cb9572$66bc54e0$3434fea0$@com> <20101206195623.GA11981@kroah.com> <003101cb958a$acfdf0e0$06f9d2a0$@com> Message-ID: 2010/12/6 Mitch Szanyi : > Hi Greg, > > I will need to confirm what the ID's are as some use the Atheros default > while others are changed to our internal ID's. The non standard frequencies > may need some tweaking but I will also need to verify what specific chipsets > you already have drivers for and what ones you may not. > As I am new in regards to working with the opensource community, may I ask > if there is anything you may need from a company n our position as well? We > have many customers working with opensource drivers for our devices as well > as firmware packages and they are all pushing us to take a proactive > approach to assisting the community, this assisting them. > Please release the firmware for your devices on terms which allow inclusion in the mainline linux kernel firmware package. This provides true out of the box support for your device in all distributions of Linux. Best regards, Maciej Grela From mszanyi at gmail.com Mon Dec 6 22:10:34 2010 From: mszanyi at gmail.com (Mitch Szanyi) Date: Mon, 6 Dec 2010 17:10:34 -0500 Subject: FW: Request for driver development In-Reply-To: <20101206212241.GA5519@kroah.com> References: <000001cb9572$66bc54e0$3434fea0$@com> <20101206195623.GA11981@kroah.com> <003101cb958a$acfdf0e0$06f9d2a0$@com> <20101206212241.GA5519@kroah.com> Message-ID: <004101cb9592$7a7ff0c0$6f7fd240$@com> Great, Thanks -----Original Message----- From: Greg KH [mailto:greg at kroah.com] Sent: Monday, December 06, 2010 4:23 PM To: Mitch Szanyi Cc: prjmgr at linuxdriverproject.org Subject: Re: FW: Request for driver development On Mon, Dec 06, 2010 at 04:15:12PM -0500, Mitch Szanyi wrote: > Hi Greg, > > I will need to confirm what the ID's are as some use the Atheros default > while others are changed to our internal ID's. The non standard frequencies > may need some tweaking but I will also need to verify what specific chipsets > you already have drivers for and what ones you may not. Sure, just ask. Or better yet, you can try out a latest kernel from www.kernel.org and let us know which devices of yours do not work. > As I am new in regards to working with the opensource community, may I ask > if there is anything you may need from a company n our position as well? We > have many customers working with opensource drivers for our devices as well > as firmware packages and they are all pushing us to take a proactive > approach to assisting the community, this assisting them. For wireless drivers and devices like yours, it's best for you to work directly with the wireless developers. They can be found on the linux-wireless at vger.kernel.org mailing list. This is especially true as odds are, all you need is a few new device ids added to the existing drivers, something that would be very trivial for those developers to do. Hope this helps, greg k-h From richih.mailinglist at gmail.com Wed Dec 8 12:16:56 2010 From: richih.mailinglist at gmail.com (Richard Hartmann) Date: Wed, 8 Dec 2010 13:16:56 +0100 Subject: Request for linux drivers for IDS uEye USB cameras -- we will ship you the hardware and you can keep it Message-ID: Hi all, as Hans de Goede does not have enough free time to go after this, he asked me to poke the V4L list. As this also concerns Linux in general, I am sending to the Linux Driver Project as well. [0] says to mail prjmgr@ for new projects so I am doing that. Finally, I wasn't sure if mailing LKML would reach people who might reasonably be interested in this offer yet miss it due to not reading the other two lists. I am still unsure but decided to default to the save option especially as one additional email to LKML is a drop in an insanely-sized bucket, anyway. We have two USB cameras by IDS Imaging [1], the uEye XS [2] and the uEye LE [3] which require a proprietary blob [4] to run under Linux. There is an user-space API of questionable usefulness. We would prefer native V4L support which actually works over said Linux "solution". The USB IDs are: Bus 002 Device 007: ID 1409:1645 # uEye U|164xLE-C Bus 002 Device 002: ID 1409:1008 # uEye U|1008XS-C (seems to be a Sony package meant for phones with IDS stuff around it) The full output lsusb -v can be found at http://paste.debian.net/100555/ - the first entry is my mouse :p The text on chips on the LE is: CY22150FZ XC 1007 A 02 609214 2400P ED4Ca 464WP K018 Output from usbmon [5] is attached. It's only 344 kiB in size so I decided to attach it for everyone's convenience. In case any list filters out attachments, just poke me and I'll send them your way. More stuff: * We will ship the cameras we bought to you. Preferably to a location where shipping costs are not insane; Europe preferred. You keep the cameras; they are yours. * You try and get pictures out of the cams. We don't need HD or anything. Our use case is criminal investigation so pics don't need to be print perfect. * The XS has auto focus and can somewhat dynamically adapt to different lighting situations. Ideally, this should work. * Hans will advise us on who of the volunteers, if any, are best suited for this. I don't know the V4L community; he does. If we get volunteers via the Linux Driver Project, I don't know how people are selected, but I am happy to go with whatever they propose. * While we know that no guarantees of any kind can be made, we obviously prefer fast results over slower ones. If someone has gobs of time available and is looking for a end-of-year project, that is a huge plus :p That being said, we don't expect miracles. * As the cameras were not cheap, we would appreciate, but do not require, a short mention in the initial commit message[s]. As an aside, if anyone can point us to any small (around thumb size or smaller) cameras, both with really wide angle and narrow angle, that connect via USB, FireWire, or Ethernet and are well-supported under Linux... we are all ears. The pictures will need to be fed into zoneminder, other than that, we don't really care how we get the pics as long as it's reliable and supported for the longer term. One would assume that dozens of webcams would fit the bill, but most of the ones I could find have been EOLed for ages. Thanks, Richard [0] http://www.linuxdriverproject.org/foswiki/bin/view/Main/MailingLists [1] http://www.ids-imaging.com/ [2] http://www.ids-imaging.com/frontend/products.php?cam_id=125 [3] http://www.ids-imaging.com/frontend/products.php?cam_id=48 [4] http://www.ueyesetup.de/frontend/files/uEyeupdater/Setup_e.htm [5] http://people.redhat.com/zaitcev/linux/usbmon-6.tar.gz -------------- next part -------------- A non-text attachment was scrubbed... Name: logs.tbz Type: application/x-bzip-compressed-tar Size: 351460 bytes Desc: not available URL: