On Sun, Jul 10, 2022 at 07:59:01PM +0300, Dima Veselov wrote:
> Greetings,
>
> I am using NetBSD 9_STABLE and I would like to connect UPS via USB serial
> port. UPS is detected as ugen device
>
> port 2 addr 3: low speed, self powered, config 1, Smart-UPS 750 FW:651.13.I
> USB FW:7.3(0x0002), A
On 10/07/2022 19:31, Greg Troxel wrote:
Dima Veselov writes:
Greetings,
I am using NetBSD 9_STABLE and I would like to connect UPS via USB serial
port. UPS is detected as ugen device
port 2 addr 3: low speed, self powered, config 1, Smart-UPS 750 FW:651.13.I
USB FW:7.3(0x0002), American
On Sun, Jul 10, 2022 at 15:38:05 +, Chavdar Ivanov wrote:
> Without any intention of stealing the topic, talking about vioscsi, I found
> a small curio today - my disks attached to vioscsi are detected only when my
> VirtualBox host is configured to use UEFI (and that is the sole difference).
Dima Veselov writes:
> Greetings,
>
> I am using NetBSD 9_STABLE and I would like to connect UPS via USB serial
> port. UPS is detected as ugen device
>
> port 2 addr 3: low speed, self powered, config 1, Smart-UPS 750 FW:651.13.I
> USB FW:7.3(0x0002), American Power Conversion(0x051d), rev 0.
Greetings,
I am using NetBSD 9_STABLE and I would like to connect UPS via USB serial
port. UPS is detected as ugen device
port 2 addr 3: low speed, self powered, config 1, Smart-UPS 750 FW:651.13.I
USB FW:7.3(0x0002), American Power Conversion(0x051d), rev 0.06(0x0006), serial
AS0714242055
s
On 10 July 2022 11:13:17 (+01:00), Robert Elz wrote:
> Date: Sun, 10 Jul 2022 11:09:40 +0200
> From: Martin Husemann
> Message-ID: <20220710090940.ga16...@mail.duskware.de>
>
> | Yeah, I noticed that we already have support for vioscsi* at virtio?
> | [which is what the spec draft I linked en
Date:Sun, 10 Jul 2022 11:09:40 +0200
From:Martin Husemann
Message-ID: <20220710090940.ga16...@mail.duskware.de>
| Yeah, I noticed that we already have support for vioscsi* at virtio?
| [which is what the spec draft I linked ended in] and vioif* at virtio?
| (at
On Sun, Jul 10, 2022 at 04:00:32PM +0700, Robert Elz wrote:
> It isn't impossible that these are the same basic virtio interfaces as
> Virtualbox/VMware/... use, just with a different manufacturer ID. But
> I'm not sure how to find out.
Yeah, I noticed that we already have support for vioscsi* a
Date:Sun, 10 Jul 2022 09:58:48 +0200
From:Martin Husemann
Message-ID: <20220710075848.gc25...@mail.duskware.de>
| Is this the spec for the virtual devices?
| https://lists.gnu.org/archive/html/qemu-devel/2011-06/msg00754.html
No idea. That's 11 years old, a
On Sun, Jul 10, 2022 at 02:23:16PM +0700, Robert Elz wrote:
> There are no drivers for those missing virtio devices in HEAD at the
> minute (or not that I could find) so NetBSD 10 isn't likely to have
> them either - not impossible, someone with the knowledge how, and the
> need to have them work,
Date:Sun, 10 Jul 2022 12:38:35 +0530
From:Mayuresh
Message-ID: <20220710070835.k6zo2mypvydnetzx@localhost>
| One more observation. For Intel CPUs across the range NetBSD recognizes
| the disk and network. For AMD CPUs it doesn't.
That has to be related to how the
On Sun, Jul 10, 2022 at 02:23:16PM +0700, Robert Elz wrote:
> There are no drivers for those missing virtio devices in HEAD at the
> minute (or not that I could find) so NetBSD 10 isn't likely to have
> them either - not impossible, someone with the knowledge how, and the
> need to have them work,
On Sun, Jul 10, 2022 at 12:19:29PM +0530, Mayuresh wrote:
> Unfortunately among stock images there are only these: Ubuntu, Fedora,
> Debian, CentOS, Rocky Linux. Even for Windows one has to pick one of these
> and use Windows iso to install.
One more observation. For Intel CPUs across the range Ne
13 matches
Mail list logo