I guess you are having a lovely weekend.My name is Wesley,I know this may seem
inappropriate so i ask for your forgiveness.I hope this email meet you in good
health condition.I`m Sorry for intruding upon your privacy. I`m from the State
.I am very cheerful, kind and positive man, and I am
Am Wes ze Stanów Zjednoczonych, ale obecnie przebywa w Syrii na misji
pokojowej. Obecnie szukam przyjaźni, która doprowadzi do związku, w którym
znowu czuję się kochana ...
Chcę cię lepiej poznać, jeśli mogę być odważny. Uważam się za łatwego człowieka
..
Proszę wybaczyć moje manie
Am Wes from United States but currently in Syria for peace keeping mission. I
am currently looking for friendship that will lead to relationship in which I
feel loved again.
I want to get to know you better, if I may be so bold. I consider myself an
easy-going man..
Please for
On Thu, 2013-04-11 at 08:15 -0700, Greg KH wrote:
> Fair enough, although this driver would probably be the least of our
> worries if that were to happen :)
Of course.
> Documenation/stable_api_nonsense.txt
Tactfully named. :)
Is there a document that describes how to track the progress a patch
m
On Thu, 2013-04-11 at 06:45 -0700, Greg KH wrote:
> I only have one very minor question about the code:
>
> > +++ b/drivers/usb/serial/wishbone-serial.c
> > @@ -0,0 +1,95 @@
> > +/*
> > + * USB Wishbone-Serial adapter driver
> > + *
> > + * Copyright (C)
ng
the Etherbone protocol. A userspace library is required to
speak the protocol made available by this driver as ttyUSBx.
Signed-off-by: Wesley W. Terpstra
---
drivers/usb/serial/Kconfig | 17 ++
drivers/usb/serial/Makefile |1 +
drivers/usb/serial/wishbone-serial.c
On Wed, 2013-04-10 at 10:08 -0700, Greg KH wrote:
> On Wed, Apr 10, 2013 at 07:01:40PM +0200, Wesley W. Terpstra wrote:
> > Greg, I've attached a small Linux driver which recognizes and the
> > USB-Wishbone functionality of the device. It just adds two vendor
> > mess
On Wed, 2013-04-10 at 19:01 +0200, Wesley W. Terpstra wrote:
> I've attached the output of lsusb -v
... and of course attached the output of an older version of the device.
The capabilities should read:
CDC ACM:
bmCapabilities 0x02
line coding and seri
.open = &usb_wb_open,
.close = &usb_wb_close,
};
static int __init usb_wb_init(void)
{
int retval;
retval = usb_serial_register(&usb_wb_device);
if (retval)
return retval;
retval = usb_register(&usb_wb_driver);
if (retval)
usb_serial_deregister(&usb_wb_device);
return retv
On Thu, 2013-03-28 at 09:39 -0500, Dan Williams wrote:
> Greg's right, there's no reason not to use cdc-acm if you want to do
> that, since not all cdc-acm devices are modems. If you get a USBIF
> vendor ID, then I'll happily add your device to the ModemManager probing
> blacklist too.
Yes, the c
On Wed, 2013-03-27 at 13:06 -0700, Greg KH wrote:
> > Our current prototypes borrow the Sierra VID
> And the USB-IF might revoke your vendor id, if they find you shipping a
> device with a different vendor id than the one you have been assigned.
One of the reasons we borrowed that VID is that we d
Good evening,
We are developing a custom piece of hardware that provides the
equivalent of two serial console interfaces. They do not speak the AT
command set. One port provides an interactive console to the user for
configuration purposes (via minicom/etc). The other speaks a proprietary
protocol
12 matches
Mail list logo
