On Tue, Nov 12, 2019 at 05:45:38PM +0100, Florian Obser wrote:
> Did I get this right? I'd appreciate it if someone could give this a
> once over.
>
> Since resolve() switched to a callback mechanism all uw_resolver objects
> pass through resolve() and either asr_resolve_done() or
> u
On Wed, Nov 13, 2019 at 06:40:00PM -0700, Aaron Bieber wrote:
> Hi,
>
> I have a raspberry pi 0 that attaches as:
> cdce0 at uhub0 port 3 configuration 2 interface 0 "Linux 4.19.75+ with \
> 2098.usb RNDIS/Ethernet Gadget" rev 2.00/4.19 addr 10
>
> Unfortunately the cdce interface does
Hi,
I have a raspberry pi 0 that attaches as:
cdce0 at uhub0 port 3 configuration 2 interface 0 "Linux 4.19.75+ with \
2098.usb RNDIS/Ethernet Gadget" rev 2.00/4.19 addr 10
Unfortunately the cdce interface does not work with this particular device.
On the linux end, it turns out that c
Apart from the obvious style(9) problems, can anyone give me guidance on
how to approach this diff? I'm quite uneasy at the amount of changes but these
nics are quite important, they're all over the place on Atom C3xxx boards
which are pretty much the main "next step up" from APUs.
I have an A2SDi
On 12/11/2019 19:02, Renaud Allard wrote:
On 12/11/2019 08:29, Theo de Raadt wrote:
Renaud, please test it for me like this:
sysupgrade -d /
This interface is dangerously incorrect.
What about this one?
ping.
I haven't seen any reply on the prefix based patch, but what about a
On Sat, Nov 02, 2019 at 06:40:52AM +0900, Iori YONEJI wrote:
> On Tue, Oct 29, 2019 at 02:17:28AM -0700, Mike Larkin wrote:
> > On Thu, Oct 24, 2019 at 08:54:58AM +0900, Iori YONEJI wrote:
> > > Hello tech@,
> > >
> > > Here is the patch discussed in the previous email. This part mainly
> > > cove
