On Tue, Dec 19, 2023 at 7:06 AM Nick Hudson wrote:
>
> On 19/11/2023 21:45, sc.dy...@gmail.com wrote:
> > hi,
> >
> > Attached patch should add support AX88179A.
>
> I committed this.
Thank you.
>
> Thanks,
> Nick
>
hi,
Attached patch should add support AX88179A.
--- src/sys/dev/usb/if_axen.c.orig 2022-08-20 23:30:49.194557768 +
+++ src/sys/dev/usb/if_axen.c 2023-11-19 20:56:42.716569803 +
@@ -52,6 +52,12 @@ struct axen_type {
uint16_taxen_flags;
#define AX178A
On 2023/11/19 11:53, Michael van Elst wrote:
> On Sun, Nov 19, 2023 at 06:40:19AM +, sc.dy...@gmail.com wrote:
>
> There are regular Ethernet headers (padded/align with 0x).
>
>> 1700366741.414702 axen_uno_rx_loop#0@0: 207b d26f4276 00e04c53 44580800
>>
hi,
On 2023/11/13 13:28, Michael van Elst wrote:
> mak...@ki.nu (Makoto Fujiwara) writes:
>
>> I've compared to openbsd: if_axen.c
>> https://raw.githubusercontent.com/openbsd/src/master/sys/dev/usb/if_axen.c
>> to N, and there are so many differencies.
>
>> Does this (N) if_axen.c works on
On 2023/11/15 23:53, sc.dy...@gmail.com wrote:
> Could you please try this patch?
Sorry, previous patch was wrong.
I was confused.
As a result, this patch changes nothing.
Perhaps 179A should work in compat mode by default.
--- src/sys/dev/usb/if_axen.c.orig 2022-08-20 23:30:49.194557768
Could you please try this patch?
--- src/sys/dev/usb/if_axen.c.orig 2022-08-20 23:30:49.194557768 +
+++ src/sys/dev/usb/if_axen.c 2023-11-15 23:23:29.684547881 +
@@ -52,6 +52,7 @@ struct axen_type {
uint16_taxen_flags;
#define AX178A 0x0001 /*
hi,
On 2023/11/13 12:29, Makoto Fujiwara wrote:
> Hi,
> I have following device:
> -
> axen0 at uhub3 port 1
> axen0: ASIX (0x0b95) AX88179A (0x1790), rev 2.10/2.00, addr 3
> axen0: AX88179
> ukphy0 at axen0 phy 3: OUI 0x00e038, model 0x0006, rev. 1
> ukphy0: 10baseT,
On 2022/10/04 10:33, adr wrote:
> On Mon, 3 Oct 2022, Michael van Elst wrote:
Yes, almost all USB audio devices work. We don't support the audio 2.0
standard (that's the >= 192kHz 24bit devices).
>>> Ok, thanks for the info.
>>
>> A patch, slightly modified by me, for xhci
On Wed, Jul 20, 2022 at 2:14 PM Patrick Welche wrote:
>
> [I posted this to port-arm around 4th July, but hasn't made it. Reposting
> here in case useful...]
>
>
> tl;dr On a raspberry pi zero W, updating the firmware allows the disable-bt
> overlay to function resulting in a stable serial
On 2022/05/14 13:47, Taylor R Campbell wrote:
> Can you please try the two attached patches?
>
> 1. uvideobadstream.patch should fix the _crash_ when you try to open a
>video stream on a device that the driver deemed to have a bad
>descriptor. Try this one first, if you have time --
I've updated the current kernel on rpi4 to 29 Apr from 14 Apr,
and got same panic for my webcam [*1].
After bisecting, it appears that dev/usb/uvideo.c rev 1.77 works,
but 1.79 does not.
When executing 'videoctl -a', vs->vs_default_format in uvideo_open
of 1.79 remains NULL.
Copying structure
On 2020/03/20 07:21, Nick Hudson wrote:
>
>
> On 19/03/2020 09:19, sc.dy...@gmail.com wrote:
>> On 2020/03/19 07:10, Nick Hudson wrote:
>>> On 19/03/2020 07:05, sc.dy...@gmail.com wrote:
On 2020/02/17 21:33, Nick Hudson wrote:
>>>
>>> [snip]
>>>
> xhci could do better and support
On 2020/03/19 07:10, Nick Hudson wrote:
> On 19/03/2020 07:05, sc.dy...@gmail.com wrote:
>> On 2020/02/17 21:33, Nick Hudson wrote:
>
> [snip]
>
>>> xhci could do better and support multiple DMA segments, but uvm could
>>> also help.
>>
>> To access each DMA segment in usb_dma_t *dma, should it
On 2020/02/17 21:33, Nick Hudson wrote:
> On 17/02/2020 16:23, Paul Goyette wrote:
> [...]
>
>>> More info...
>>>
>>> First, this is on a amd64 system, witwh 8core/16thread and 128GB of RAM.
>>>
>>> On IRC it was suggested (thanks, maya!) that the error message might be
>>> related to memory
On Fri, May 10, 2019 at 6:08 AM Mayuresh wrote:
>
> On Fri, May 10, 2019 at 06:05:34AM +0000, sc dying wrote:
> > Attached files look bogus, I'll resend.
>
> Due to some other compulsions (a lot of pkgs that I need not building
> under current, discussed on various t
On Fri, May 10, 2019 at 5:56 AM sc dying wrote:
> Either of attached patch might help you.
Attached files look bogus, I'll resend.
urndis.diff
Description: Binary data
dwc2.diff
Description: Binary data
hi,
On 2019/05/03 03:23, Mayuresh wrote:
> On Thu, May 02, 2019 at 09:23:38PM +0530, Mayuresh wrote:
>> # uname -a
>> NetBSD pi 8.99.37 NetBSD 8.99.37 (RPI2) #1: Thu Apr 25 16:01:51 UTC 2019
>> root@pi:/usr/src/sys/arch/evbarm/compile/RPI2 evbarm
>>
>> # dmesg | grep urndis
>> [47.388677]
On 2017/08/22 16:57, Nick Hudson wrote:
> On 08/22/17 17:08, sc dying wrote:
>> On Tue, Aug 22, 2017 at 2:18 PM, Nick Hudson <sk...@netbsd.org> wrote:
>>> On 08/21/17 14:56, sc dying wrote:
>>>> On 2017/08/21 12:00, Nick Hudson wrote:
>>>>> On
It looks like case USB_REQUEST in usbioctl() of usb.c misses `break.'
--- sys/dev/usb/usb.c Sun Jan 29 02:28:16 2017
+++ sys/dev/usb/usb.c Mon Aug 28 08:53:56 2017
@@ -775,6 +775,7 @@ usbioctl(dev_t devt, u_long cmd, void *d
len = UGETW(ur->ucr_request.wLength);
kmem_free(ptr, len);
}
+
On Tue, Aug 22, 2017 at 2:18 PM, Nick Hudson <sk...@netbsd.org> wrote:
> On 08/21/17 14:56, sc dying wrote:
>>
>> On 2017/08/21 12:00, Nick Hudson wrote:
>>>
>>> On 08/16/17 06:42, sc dying wrote:
>>>>
>>>> When ukbd(4) is a
On 2017/08/21 12:00, Nick Hudson wrote:
> On 08/16/17 06:42, sc dying wrote:
>> When ukbd(4) is a console and connected to USB3 port, you can enter
>> into DDB by pressing ALT+CTRL+ESC but console freezes.
>> (on HEAD, netbsd-7, netbsd-8)
>>
>> xhci has two bus
On 2017/04/22 12:57, Gary Duzan wrote:
>Booting from the installer image, I noticed a couple of USB related
> issues. First, the boot menu wouldn't recognize my USB keyboard;
> I had to hit ENTER on my PS/2 keyboard to get the boot to continue.
> Then the boot process stopped after probing
Is the condition at line 1919 of ic/rtl8169.c inverted?
It should be `!=' to make it act as before patch when
RTKQ_IM_HW is disabed in if_re_pci.c.
23 matches
Mail list logo
