2003-06-12T17:21:01 Greg Brigley:
> Thanks, I wasn't aware that winpcap could send as well as receive.
Very, very good point, I'd completely forgotten about that, libpcap
is just the sniffer half.
Its complement is libnet, and it seems to have Windows support as
well.
Somehow I forget that this
Thanks, I wasn't aware that winpcap could send as well as receive. I'll keep
that option in mind.
Greg
On Thursday 12 June 2003 13:55, Bennett Todd wrote:
> 2003-06-12T13:20:38 Greg Brigley:
> > :) Yes. From an implementation perspective, using the network
> >
> > sounds simpler and more flex
2003-06-12T13:20:38 Greg Brigley:
> :) Yes. From an implementation perspective, using the network
> sounds simpler and more flexible. But going without it reduces
> the amount of configuration our users have to do, and the amount
> of support that we have to do.
I just occurred to me, any possib
On Tuesday 10 June 2003 21:04, David Brownell wrote:
> That is, it's a USB host.
Yes
>
> Unidirectional is probably bad, you'd need some status exchange.
I wondered about that, but I figured I'd start by hoping for the best possible
case.
> There's the DFU class spec, which resembles overkil
Greg Brigley wrote:
I'd like to use a USB bridge cable for updating the firmware in an embedded
linux device from a Windows box. The device features a USB A port but no B
port. I'd like to distribute a bridge cable and a custom windows app, and
instruct the user to merely run the app and plug
I'd like to use a USB bridge cable for updating the firmware in an embedded
linux device from a Windows box. The device features a USB A port but no B
port. I'd like to distribute a bridge cable and a custom windows app, and
instruct the user to merely run the app and plug in the cable.
As I
