I'm not sure about this chunk.
There are fdti chipsets that expose two uftdi, with a ucom each.
But maybe there are chipsets that expose one uftdi, which has two ucom?
It could be saying such a model is not supported.
If that is the gap, it is wrong to say ucom needs extending. uftdi would
With A-MSDUs enabled in -current people are seeing a lot of
input packet decapsulations failed
events in netstat -W iwm0.
This fixes the issue on iwm 8265 for me. There are between 6 and 8 bytes of
trailing data in the A-MSDU frame buffer. This results in a decap failure
being counted
On Wed, Dec 09, 2020 at 09:11:35AM +0100, Jan Klemkow wrote:
> On Tue, Dec 08, 2020 at 09:03:53PM -0300, Daniel Bolgheroni wrote:
> > I have a FT232H variant (marked FT232HQ, 0403:6014) which works with
> > uftdi(4).
> >
> > Still related to uftdi(4), sys/dev/usb/ftdi.c has a comment saying
On Wed, Dec 09, 2020 at 09:11:35AM +0100, Jan Klemkow wrote:
> On Tue, Dec 08, 2020 at 09:03:53PM -0300, Daniel Bolgheroni wrote:
> > I have a FT232H variant (marked FT232HQ, 0403:6014) which works with
> > uftdi(4).
> >
> > Still related to uftdi(4), sys/dev/usb/ftdi.c has a comment saying
This diff makes the timer code independent from struct peer. This way
it can be used in different places without too much issues.
OK?
--
:wq Claudio
Index: control.c
===
RCS file: /cvs/src/usr.sbin/bgpd/control.c,v
retrieving
On Tue, Dec 08, 2020 at 09:03:53PM -0300, Daniel Bolgheroni wrote:
> I have a FT232H variant (marked FT232HQ, 0403:6014) which works with uftdi(4).
>
> Still related to uftdi(4), sys/dev/usb/ftdi.c has a comment saying uftdi(4)
> does not support multiple serial ports because ucom(4), but I'm
On Tue, Dec 08, 2020 at 11:36:37PM -0700, jo...@armadilloaerospace.com wrote:
> The game battlestar has source files names com1.c through com7.c, which
> are illegal on windows due to ancient dos com port rules.
>
> I understand there might not be much sympathy for that, but being able
> to have
Den ons 9 dec. 2020 kl 09:20 skrev :
> The game battlestar has source files names com1.c through com7.c, which
> are illegal on windows due to ancient dos com port rules.
>
> I understand there might not be much sympathy for that, but being able
> to have the full source tree on a windows system
