On Wed, Sep 05, 2018 at 08:11:41AM +, Yeh.Charles [葉榮鑫] wrote:
> Hi all,
> I am a software engineer from Prolific.
> Do you have received the following email?
> Prolific has new USB to UART chip, we need to update new driver to
> Linux kernel.
Yes, we did, but you sent the em
On Wed, Sep 05, 2018 at 10:54:00AM +, Yeh.Charles [葉榮鑫] wrote:
> Hi All,
>
> The "confidential" message is auto add by email server, please ignore it
Sorry, but I can not just "ignore it". Talk to your corporate lawyers
for why that is the case.
greg k-h
On Wed, Sep 05, 2018 at 10:51:52AM +, Yeh.Charles [葉榮鑫] wrote:
> Hi Greg,
> Because the VENDOR_WRITE_REQUEST & VENDOR_READ_REQUEST is different
> between old and new chip.
>
> VENDOR_WRITE_REQUESTVENDOR_READ_REQUEST
> PL2303 (old chip) 0x01
On Tue, Mar 05, 2013 at 01:23:33PM +0100, Bjørn Mork wrote:
> As you are well aware of, we parse descriptors as needed on Linux and
> can just as easy support the Windows look'n'feel if required. There is
> absolutely no need to create special Linux descriptors to adapt to
> existing drivers. We'
On Thu, Jul 26, 2012 at 08:44:33AM +, Fangxiaozhi (Franko) wrote:
> From: fangxiaozhi
> 1. This patch is based on the kernel of 3.5
> 2. In this patch, we add new micro for matching the series USB devices with
> vendor ID and interface information.
> 3. In this patch, we add new declarations
On Wed, Aug 01, 2012 at 02:05:18AM +, Fangxiaozhi (Franko) wrote:
> From: fangxiaozhi
> 1. This patch is based on the kernel of 3.5
> 2. In this patch, we add new micro for matching the series USB devices with
> vendor ID and interface information.
> 3. In this patch, we add new declaration
On Wed, Aug 08, 2012 at 01:57:06AM +, Fangxiaozhi (Franko) wrote:
> Dear Greg：
>
> Sorry, this email has included the whole patch. 1/8, I mean that it is submit
> at Aug. 1st.
No, please don't put the date in the Subject:, that's what the normal
Date field in the email is for :)
> By the way
On Thu, Apr 10, 2014 at 07:59:38AM +, Narasimharao Bolisetti wrote:
>
> Hi,
>
> I have checked the same in the recent kernel versions also. Issue is still
> remain.
What versions have you tried, and what are the logs from those versions?
> ::DISCLAIMER::
> -
On Tue, Apr 07, 2015 at 05:33:31PM +, Mark Enstone wrote:
> Greg,
Please resend without using html email so it gets through to the
linux-usb mailing list.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.ker
On Fri, Jun 26, 2015 at 01:43:00AM +, Chu.Mike [朱堅宜] wrote:
> Hi Greg,
>
> We have a new PL2303 chip version (called PL2303TB) with 12 GPIO function.
> http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=235&pcid=41
>
> I attached here the Linux driver and GPIO sample code. Can you help to
>
On Thu, Jan 25, 2018 at 03:44:46AM +, Chu.Mike [朱堅宜] wrote:
> Dear Johan / Greg,
>
> We have a new customer who wants to add their VID/PID to the PL2303 driver
> source.
> Can you help me?
>
> Customer: Chilitag
> VID: 067B
> PID: AAA8
>
> { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID_CH
On Thu, Jan 25, 2018 at 09:37:16AM +, Chu.Mike [朱堅宜] wrote:
> Thanks, guys! Do you know what kernel version will I find this addition?
It will get merged into Linus's tree in the 4.16-rc1 merge window, and
then get backported to all of the stable kernel trees within a week or
so after that hap
On Fri, Jul 14, 2017 at 05:10:57AM +, Yeh.Charles[葉榮鑫] wrote:
> Hi Greg,
>The attached file" pl2303c_patch.zip & pl2303h_patch.zip" are patch file
> for PL2303.c & PL2303.h.
>Can you help to include it to the next kernel release?
Hm, I started to edit this to make it fit the proper co
On Fri, Jul 14, 2017 at 10:32:49AM +, Chu.Mike [朱堅宜] wrote:
> Hi Greg,
>
> This patch is for adding our new chip PL2303TB (UART, 12 GPIO, PWN)
> PID is 2304 and GPIO function codes. Attached is datasheet. Can you
> help us?
Adding a new device is is simple, but adding custom ioctls for gpio
c
14 matches
Mail list logo
