Hello. Thank you very much. Indeed the umodem(4) recognized the
device, but I missed the
dmesg output.
thanks for the tip.
-Brian
buh...@nfbcal.org (Brian Buhrow) writes:
> hello. Does anyone know what USB serial chip the Cisco USB serial
> console is closest to
>in our USB serial drivers list? the vendor code for the device I'm talking
>about is: 0x05a6
>and the product code is: 0x0009.
The umodem(4) driver is fo
On Tue, Jun 01, 2021 at 10:08:55AM -0700, Brian Buhrow wrote:
> hello David. What I don't see in your proposal is a way of
> implementing a dynamic device filesystem.
As I already posted about once, that's irrelevant to what I'm
proposing.
A working devfs that can be used in all places wh
hello. Does anyone know what USB serial chip the Cisco USB serial
console is closest to
in our USB serial drivers list? the vendor code for the device I'm talking
about is: 0x05a6
and the product code is: 0x0009. It doesn't look like we have a driver that
recognizes these
codes, but I
wo...@planix.ca ("Greg A. Woods") writes:
>My understanding w.r.t. the rationale FreeBSD used in deciding to remove
>the block devices was that FreeBSD never really buffered/cached by
>device in the first place. Also, according to PHK in his 2002 BSDCan
>paper about FreeBSD's /dev, "In FreeBSD bl
