From: "Wojciech A. Koszek" <wojciech@koszek.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Improved fxload [Was: Re: fxload devpath]
Date: Mon, 19 Oct 2015 05:53:05 +0000 [thread overview]
Message-ID: <56248541.6050405@koszek.com> (raw)
In-Reply-To: <561B3ADF.5010308@koszek.com>
Carl,
Thanks for testing. I gave you the credit for mentioning
LIBUSB_SUPPORT=1. I forgot about it.
W.
On 10/13/15 10:52 AM, Carl Karsten wrote:
> looks like I need to set LIBUSB_SUPPORT
> $ LIBUSB_SUPPORT=1 make
>
> And now it is working as described, which is very nice.
> +1 mainline
>
> Q: What happens if there are 2 devices plugged in?
>
> I am assuming it uses the first one it finds.
> For my usage that is fine.
> You might want to add an index or something, although in those cases
> the person can just use the devpath. I expect most people will be
> using this from a udev rule that acts on the device being plugged in.
>
>
> On Sun, Oct 11, 2015 at 11:45 PM, Wojciech A. Koszek
> <wojciech@koszek.com> wrote:
>> Hello,
>>
>> In May 2010 I've fixed fxload by adding LibUSB support.
>>
>> After seeing Carl's e-mail I dug out a patches from backup, and made a repo
>> out of it:
>>
>> https://github.com/wkoszek/fxload
>>
>> So basically fxload would gain LibUSB support and much easier usage, since
>> the paths which fxload requires right now change for some devices doing
>> re-enumeration.
>>
>> Back then I failed to get any replies. Retrying now in hope we could get
>> these fixes into mainline.
>>
>> Thanks,
>>
>> Wojciech
>>
>> On 10/11/15 8:23 PM, Andrei Borzenkov wrote:
>>> 12.10.2015 01:29, Carl Karsten пишет:
>>>> man fxload - Firmware download to EZ-USB devices
>>>>
>>>> fxload [ -v ] [ -l ] [ -D devpath ] ...
>>>>
>>>> -D devpath
>>>> Specifies the "usbfs" path name for the device in
>>>> question, such
>>>> as /proc/bus/usb/004/080. This takes precedence over any
>>>> DEVICE
>>>> environment variable that may be set.
>>>>
>>>> How do I figure out what the devpath is for the device I plugged in?
>>>>
>>>> or.. how do I know what devnum will get assigned?
>>>>
>>>> The device(s) I am working with:
>>>>
>>>> juser@dc10b:~$ lsusb -s 2:9; lsusb -s 2:10
>>>> Bus 002 Device 009: ID 04e2:1410 Exar Corp.
>>>> Bus 002 Device 010: ID 1443:0007 Digilent Development board JTAG
>>>>
>>> Should be /dev/bus/usb/002/010 etc.
>>>
>>>> Ubuntu trusty lts
>>>> Linux dc10b 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC
>>>> 2015 x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> --
>>>> Carl K
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-hotplug"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-hotplug"
>>> in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
prev parent reply other threads:[~2015-10-19 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 4:45 Improved fxload [Was: Re: fxload devpath] Wojciech A. Koszek
2015-10-12 5:41 ` Carl Karsten
2015-10-13 17:52 ` Carl Karsten
2015-10-14 8:47 ` Xiaofan Chen
2015-10-19 5:53 ` Wojciech A. Koszek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56248541.6050405@koszek.com \
--to=wojciech@koszek.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).