On Wed, Jul 31, 2019 at 07:32:29PM +0200, Markus Breunig wrote:
>
>
> Am 16.07.2019 um 11:23 schrieb Johan Hovold:
> > [ Pleas avoid top posting. ]
> >
> > On Sun, Jul 07, 2019 at 09:38:00PM +0200, Markus Breunig wrote:
> >> Hi Greg,
> >>
> >> also the company GNS has a fragmented homepage, the h
Am 16.07.2019 um 11:23 schrieb Johan Hovold:
[ Pleas avoid top posting. ]
On Sun, Jul 07, 2019 at 09:38:00PM +0200, Markus Breunig wrote:
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist
available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a l
[ Pleas avoid top posting. ]
On Sun, Jul 07, 2019 at 09:38:00PM +0200, Markus Breunig wrote:
> Hi Greg,
>
> also the company GNS has a fragmented homepage, the handbook ist
> available here:
> http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
> habe a look to page 10 "Remarks to Linux"
>
>
Hi Greg,
also the company GNS has a fragmented homepage, the handbook ist
available here:
http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf
habe a look to page 10 "Remarks to Linux"
This is the log of "lsusb -v" (full scan result attached):
Bus 001 Device 004: ID 04d8:f8e8 Microchip Techno
On Thu, Jul 04, 2019 at 10:47:47PM +0200, Markus Breunig wrote:
> Hi Greg,
>
> using a serial device driver is the idea of the manufacturer
> "www.gns-gmbh.com". In the LINUX instructions of the ADS-B receiver some
> hints to use the device are given via usbserial.
Any pointers to those instructi
pberry Pi told me to send you the following information. I hope it
helps ...
best regards
Markus
[2.081893] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[2.219804] usb 1-1.2: New USB device found, idVendor=04d8,
idProduct=f8e8, bcdDevice=48.1
ew full-speed USB device number 4 using dwc_otg
> [ 2.219804] usb 1-1.2: New USB device found, idVendor=04d8,
> idProduct=f8e8, bcdDevice=48.12
> [2.219821] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [2.219830] usb 1-1.2: Product: GNS 5890 ADS-B R
Hello,
my Raspberry Pi told me to send you the following information. I hope it
helps ...
best regards
Markus
[2.081893] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[2.219804] usb 1-1.2: New USB device found, idVendor=04d8,
idProduct
Hi Johan,
On 11/28/2017 05:01 PM, Johan Hovold wrote:
> On Tue, Nov 28, 2017 at 12:40:59PM +0800, Lu Baolu wrote:
>> USB vendor id and product id for Linux USB Debug Target is added.
>>
>> Signed-off-by: Lu Baolu
>> ---
>> drivers/usb/serial/usb_debug.c | 2 ++
>> 1 file changed, 2 insertions(+)
On Tue, Nov 28, 2017 at 12:40:59PM +0800, Lu Baolu wrote:
> USB vendor id and product id for Linux USB Debug Target is added.
>
> Signed-off-by: Lu Baolu
> ---
> drivers/usb/serial/usb_debug.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/serial/usb_debug.c b/drivers/us
USB vendor id and product id for Linux USB Debug Target is added.
Signed-off-by: Lu Baolu
---
drivers/usb/serial/usb_debug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/serial/usb_debug.c b/drivers/usb/serial/usb_debug.c
index ab5a2ac..47636b6 100644
--- a/drivers/usb/seria
Good news! I figured out that I can simply use
udev_device_get_is_initialized(). It does exactly what I want.
I tried using a udev_monitor but it doesn't seem to report
pre-existing devices (devices that were already connected to the
system). It just reports changes.
Thanks for the help.
--Da
On Mon, Sep 14, 2015 at 12:04 PM, Greg KH wrote:
> Start your program to listen and handle all devices that way through
> udev iterators, that way will always work (for existing and new
> devices).
If by "existing devices", you mean devices that were connected to the
computer before my program st
On Mon, Sep 14, 2015 at 11:55:17AM -0700, David Grayson wrote:
> Hello, Greg. Thanks for the quick reply, and for all your
> contributions to Linux.
>
> On Fri, Sep 11, 2015 at 6:01 PM, Greg KH wrote:
> > Can't you wait for libudev to notify your application when the usb
> > device is attached?
>
> Unfortunately, using a udev_monitor (or a libusb context) will make my
> code more complicated, because there will be a need to start the
> monitor and keep it around while we are waiting for the new USB device
> to connect. It is simpler if I can just ask the system for a list of
&
On Fri, Sep 11, 2015 at 04:54:13PM -0700, David Grayson wrote:
> Hello.
>
> In Linux, there seems to be a period of time when a newly-connected
> USB device will be detectable by libudev, but the udev rules governing
> its permissions have not been applied. This is a problem for me
> because I wa
are sent out after udev has finished
> its event processing, all rules have been processed,
> and needed device nodes are created.
Unfortunately, using a udev_monitor (or a libusb context) will make my
code more complicated, because there will be a need to start the
monitor and keep it arou
On Mon, Sep 15, 2014 at 01:48:09PM +0200, Andreas Bomholtz wrote:
> Hi,
>
> I just want to know what is need for adding a new USB device to the
> cp210x driver?
>
> The new USB Device:
>
> { USB_DEVICE(0x1D6F, 0x0010) }, /* Seluxit ApS RF Dongle */
You could send use a
Hi,
I just want to know what is need for adding a new USB device to the
cp210x driver?
The new USB Device:
{ USB_DEVICE(0x1D6F, 0x0010) }, /* Seluxit ApS RF Dongle */
Best regards,
Andreas Bomholtz
Seluxit ApS
--
To unsubscribe from this list: send the line "unsubscribe linux-usb&qu
19 matches
Mail list logo