staf...@shangtai.net (=?UTF-8?B?U3RhZmZhbiBUaG9tw6lu?=) writes:
>While I was fiddling around with it, I booted a FreeBSD-14 thumbdrive
>and there it does work as well, and their driver helpfully tells you
>what quirks it uses. This is what I found:
>umass quirks: 0xc104
>0x0004 -
ode to accept USB
access.
The product code 0x1fc9:0x000b seems to be a LPC11U24,
there is an application note AN11305 from NXP for
"USB In-System Programming with th LPC11U3X/LPC1U2X",
but I didn't find any hints in that document.
Greetings,
--
Michael van
ichael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
s need to be ignored.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
k...@munnari.oz.au (Robert Elz) writes:
>I have been meaning to suggest for ages that we remove all the
>geometry nonsense from everywhere in the kernel, except those
>drivers that actually need it.
We use that nonsense without actually knowing.
The "cylinder" value is used to sort disk
k...@munnari.oz.au (Robert Elz) writes:
>If you are able, try building a kernel with the patch below.
>I suspect this should probably apply without too many problems
>to any reasonably modern NetBSD kernel version, patch is to
>src/sys/dev/scsipi/sd.c
>+ if (dp->cyls == 0) /*
staf...@shangtai.net (=?UTF-8?B?U3RhZmZhbiBUaG9tw6lu?=) writes:
>[21.611880] scsibus1 at umass1: 2 targets, 1 lun per target
>[21.611880] sd1 at scsibus1 target 0 lun 0: 1.0> disk removable
>[21.611880] sd1: fabricating a geometry
>[21.611880] sd1: 34816, 0 cyl, 64 head, 32 sec,
only
copy out when oldp was set. sysctl will check the returned *oldlenp
against the value passed by the caller and return ENOMEM as appropriate.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark ma
i...@home.imil.net (Emile 'iMil' Heitor) writes:
>Except it does not, the first time it calls back the helper function,
>*oldlenp value is 1024 no matter what I set it to before.
>But if I return once again (either with ENOMEM or 0, doesn't matter),
>the helper function will now be called with
mo...@rodents-montreal.org (Mouse) writes:
>> Modern hardware could easily do 100kHz.
>Not with curren^Wat least one moderately recent NetBSD version!
>At work, I had occasion to run 9.1/amd64 with HZ=8000. This was to get
>8-bit data pushed out a parallel port at 8kHz; I added special-case
n at different speeds that aren't just
integer multiples.
N.B. my m68k emulator runs a HZ=100 guest without a problem. But that's
a fake, in reality it only runs 100 ticks per second on average, In
particular when the guest becomes idle.
Greetings,
--
Michael van
antage is that you can use independent timing (that's what
bites in the emulator case where guest and host clocks run at the same
rate).
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
b...@softjar.se (Johnny Billquist) writes:
>Being able to measure time with high precision is desierable, but we can
>already do that without being tickless.
We cannot delay with high precision. You can increase HZ to some degree,
but that comes at a price.
sim...@netbsd.org (Simon Burge) writes:
>qemu uses ppoll() which is implemented with pollts() to do emulated
>timers, so that doesn't help here. I don't know what simh uses, nor
>any of the other emulators.
simh uses pthread_cond_timedwait().
This actually waits using TIMER_ABSTIME for a
mo...@rodents-montreal.org (Mouse) writes:
>} else if (sec <= (LONG_MAX / 100))
>ticks = (((sec * 100) + (unsigned long)usec + (tick - 1))
>/ tick) + 1;
>which looks suspicious. If sec is zero and usec is tick, that
>expression will return 2
u...@stderr.spb.ru (Valery Ushakov) writes:
>Switching from a fixed size array to a dynamic one is probably not too
>much work either. But then, overall, I think that trying to make the
>kernel substitute for screen, tmux (in base), etc is kinda dead end,
>so I'd rather we don't encourage it.
tlaro...@kergis.com writes:
>disable {drmkms} # NEW: disable devices belonging to group "drmkms"
Almost noone would need to turn off all drmkms drivers. What you may
want to control is that a GPU isn't used as a console. Disabling a driver
is just our crude workaround to achieve this.
I
r...@sdf.org (RVP) writes:
>On Sat, 4 Nov 2023, RVP wrote:
>> 1) Allowing shell-like patterns (not hard to implement):
>>
>> uc> disable *drm* *usb$ # all with `drm' anywhere and those ending in
>>
>Ah, since these are shell-like patterns there's not need for a `$' to
>denote EOL. So:
mjgu...@gmail.com (Mateusz Guzik) writes:
>> While vnodes would be recyclable, they hardly get recycled unless
>> an filesystem object is deleted or the filesystem is unmounted.
>They get recycled all the time by vdrain thread if numvnodes goes above
>desiredvnodes, like it does in this test.
mjgu...@gmail.com (Mateusz Guzik) writes:
>Running 20 find(1) instances, where each has a "private" tree with
>million of files runs into trouble with the kernel killing them (and
>others):
>[ 785.194378] UVM: pid 1998.1998 (find), uid 0 killed: out of swap
>This should not be happening --
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>> you dump a memory block that isn't a multiple of a disk sector
>> (according to disklabel)
>You mean this one (from disklabel raid0):
> bytes/sector: 512
>?
Yes. Which makes it unlikely.
amd64/machdep.c:
this dumps at least
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>GO>Dumping to a RAID 1 set is supported in -8. But yes, none of those
>GO>values seem to align with each other. 18,1 is 'raid0b' thouugh, so that
>GO>part seems correct.
>MvE> offset and size relate to the dump data (dumplo and
k...@munnari.oz.au (Robert Elz) writes:
>Date:Mon, 25 Sep 2023 05:57:49 +
>From:Emmanuel Dreyfus
>Message-ID:
> | bootme.cfg is searched in EFI paririon /EFI/NetBSD/boot.cfg
>Which EFI partition? I think I have about 5 or 6, sprinkled around
>various
os...@netbsd.org (Greg Oster) writes:
>> dumping to dev 18,1 (offset=1090767, size=8252262):
>>
>Dumping to a RAID 1 set is supported in -8. But yes, none of those
>values seem to align with each other. 18,1 is 'raid0b' thouugh, so that
>part seems correct.
offset and size relate to the
you specify something else (or magic like the raidframe
hack comes into play).
So, the bootme flag effectively specifies the root partition, but only
by virtue of defaults being passed down the chain. The kernel should
not outguess things and interpret the flag itself.
--
a...@absd.org (David Brownlee) writes:
>Our gpt(8) states "bootme flag is used to indicate which partition
>should be booted by UEFI boot code", which could be read either way.
The flag is used to find the partition to load /boot, /boot.cfg or
the kernel from. The boot disk information is also
old dummy record with a non-empty string.
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mar...@duskware.de (Martin Husemann) writes:
>But the more general solution (which would be just as easy for the end
>user, but more flexibel) is to add support for a rootdev statement
>in boot.cfg and then put the label name or the guid there. Similar
>to evbarm taking a root=dev argument passed
On Fri, Sep 15, 2023 at 03:15:10PM +, Emmanuel Dreyfus wrote:
> On Fri, Sep 15, 2023 at 03:06:46PM -0000, Michael van Elst wrote:
> > What about just telling the kernel what to use in /boot.cfg ?
> > No need to add more magic to the kernel.
>
> Ths user took care
m...@netbsd.org (Emmanuel Dreyfus) writes:
>multitboot lets the bootloader pass boot device information as BIOS
>driver, partition number, subpartition number. This is intended
>for MBR extended partitions or MBR/disklabel.
What about just telling the kernel what to use in /boot.cfg ?
No need to
r...@fdy2.co.uk (Robert Swindells) writes:
>There is a call to panic() if the kernel detects that there is no
>console device found, I would like to make this call to it just reboot
>without dropping into ddb.
Not without modifications.
You could include the nullcons (i.e. boot without console)
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>I had a RAIDframe level 1 RAID with the first component marked as failed, e,g,
> component0: failed
> /dev/dkN: optimal
>and although the set was configured -A softroot, the kernel didn't configure
>raid0a as the root file
mar...@duskware.de (Martin Husemann) writes:
> if (flags & DKW_FLAGS_BOOTME)
> rf_boot_from_filesystem_starting_at(dkw.offset)
A flag in GPT that is supposed to be used by a bootloader now causes
changes in the kernel disk infrastructure to be used for a
different.
There might also be some difference in command queuing parameters,
some disks get slower for this kind of test.
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
g...@lexort.com (Greg Troxel) writes:
>When you run dd with bs=64k and then bs=1m, how different are the
>results? (I believe raw requests happen accordingly, vs MAXPHYS for fs
>etc. access.)
'raw requests' are split into MAXPHYS size chunks. While using bs=1m
reduces the syscall overhead
r audio driver will crudely resample this to what it
and the hardware supports.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
n...@netbsd.org (nia) writes:
Hi nia,
>I believe this should not be enabled, and that applications
>should be trained to write 32-bit linear samples instead.
Two things.
The "userland" 24bit format flag is required for internal 24bit
processing because someone thought that without 24bit
mo...@rodents-montreal.org (Mouse) writes:
>But that comment clearly indicates that _someone_ thought it
>reasonable to checksum before swapping, so I can't help wondering what
>use case that's appropriate for.
It's a checksum over the 16bit words in native byte order. So when
you access the
m...@ecs.vuw.ac.nz (Mark Davies) writes:
linux->netbsd10
>18 -> V3 SETATTR Call (Reply in 19), FH: 0xf9f94117
>19 <- V3 SETATTR Reply (Call In 18) Error: NFS3ERR_ACCESS
linux->netbsd9
>16 -> V3 SETATTR Call (Reply in 17), FH: 0xfe8a620f
>17 <- V3 SETATTR Reply (Call In 16)
m...@netbsd.org (Emmanuel Dreyfus) writes:
>I suspect a mode problem. In the boot prompt, gop displays:
>*0: 1920x1080 BGRR pitch 1920 bpp 32
> 1: 640x480 BGRR pitch 640 bpp 32
> 2: 800x600 BGRR pitch 800 bpp 32
> 3: 1024x768 BGRR pitch 1024 bpp 32
> 4: 1280x1024 BGRR pitch 1280 bpp 32
>Trying
k...@munnari.oz.au (Robert Elz) writes:
>Do we do crash dumps onto raidsets?
We can dump on raidsets, the code selects a working component or a spare
disk to dump on. Doesn't mean that it works, the more complicated the
device access gets, the less likely it will succeed.
c...@sdf.org ("Stephen M. Jones") writes:
>While it partially works, shift/shift lock key and sometimes space bar =
>does
>not seem to work properly.
Can you be specific in how it does not work properly?
>[ 11434.0227330] ukbd0 at uhidev0
>[ 11434.4428808] ums0 at uhidev1: 3 buttons
>login:
bsd...@proton.me (Salil) writes:
>sdhc0 at pci0 dev 28 function 0: vendor 8086 product 31cc (rev. 0x06)
This is the intel GLK SDHC controller.
>sdmmc0: sdmmc_mem_enable failed with error 60
>sdmmc0: autoconfiguration error: couldn't enable card: 60
>Does anyone know the resolution?
The sdhc
ed to build the kernel (not modules) and install it.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
USB drive being unplugged).
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mod is built
for a GENERIC netbsd-9 amd64 kernel and might be sufficient.
Why would the workstations require rebooting ?
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>>> For a very long time (I don't remember if it was from 9.0 or 9.1), my
>>> main server randomly panics or enters in a deadlock when it tries to
>>> access to an iSCSI NAS.
>>
>> Can you provide information about the panic?
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
> For a very long time (I don't remember if it was from 9.0 or 9.1), my
>main server randomly panics or enters in a deadlock when it tries to
>access to an iSCSI NAS.
Can you provide information about the panic? kernel
stephan...@googlemail.com (Stephan) writes:
>Hello,
>I am re-asking this question here because I have not received a reply
>on port-arm@, surprisingly.
>I am doing some experimentation with the Raspberry Pi for which I have
>set up a serial connection to another computer. Now I=C2=B4d like to
k...@munnari.oz.au (Robert Elz) writes:
>The way you have it coded, I suspect that 9.1 binaries will appear to
>be 9.1.0 instead (the ver_patch data is always appended for ver_maj >= 9).
True. Here is a patch that ignores a zero patch level.
Index: external/bsd/file/dist/src/readelf.c
campbell+netbsd-tech-k...@mumble.net (Taylor R Campbell) writes:
>We appear to have revived the old alphanumeric versioning scheme,
>according to file(1)! Someone needs to teach file(1) that this is
>9.99.100, not 9.99A(.0).
Index: external/bsd/file/dist/src/readelf.c
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>What /does/ work is setting the controller to RAID mode and create two
>volumes with a one-element RAID-0. But that feels like crazy.
That's a common setup. In particular it allows to present a "right-sized" disk
so that you can
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>> I don't remember the details (and it depends on the controller version),
>> but you need to have physical disks assigned to one (or more) RAID volume,
>> and then the RAID volume has to be exported as one (or more) virtual disks.
>But
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>> -> This is attaching a H330 (RAID version) and it gets the mfii driver.
>> mfii0 at pci1 dev 0 function 0: "PERC H330 Mini", firmware 25.5.9.0001
>OK, remains the question why I don't see any discs in bioctl.
> 0 Non-RAID
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>The other question is why the register call fails.
>According to the BIOS setup, the controller has no sensors. Could that be
>the problem?
The bio framework uses sensors so that you can watch for failed volumes.
No volumes means no
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>This is -current from around yesterday.
>I guess the problem is related to
> mfii0: autoconfiguration error: unable to register with sysmon (rv = 86)
> mfii0: autoconfiguration error: unable to create sensors
>So probably
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>> These controller chips can run two different kinds of firmware.
>> The mfii driver is for talking to the RAID firmware ("IR mode")
>> while the mpii driver is for talking to the vanilla SAS firmware
>> ("IT mode").
>Ah, and how do I
p...@whooppee.com (Paul Goyette) writes:
>On Tue, 13 Sep 2022, Edgar Fu=DF wrote:
>> It appears to me we have two drivers for the SAS3008: mfii(4) and mpii(4)=
>=2E
>> Why?
>I know nothing about these drivers, but the man pages show that mfii
>works for MegaRAID devices, while mpii deaels with
p...@whooppee.com (Paul Goyette) writes:
>Don't forget to deregister the device if the xxx_attach() later exits...
I think the point was to not do this, so that a failed attach doesn't
prevent the system from entering sleep mode.
Here, calling pmf_register first on attachment is then required,
m...@netbsd.org (Emmanuel Dreyfus) writes:
>On Wed, Aug 10, 2022 at 03:09:34PM -0000, Michael van Elst wrote:
>> That's the fan "alarm status" being FALSE, meaing, there is no
>> alarm. It's all well.
>I know one of the five fans is dead, hence I wonder what
m...@netbsd.org (Emmanuel Dreyfus) writes:
>and not even get their status. That examplains envstat(8) output
>about the fans:
> Current CritMax WarnMax WarnMin CritMin Unit
>[acpifan0]
> state: FALSE
That's the fan "alarm status" being FALSE, meaing,
m...@netbsd.org (Emmanuel Dreyfus) writes:
>Is there any way to control fans through ACPI? acpi(4) says "The acpifan
>driver does not support controlling the fan", but is it something that
>needs to be implmented, or is it not possible?
Depends. Some ACPI implementations allow you to set fan
On Sun, Jul 03, 2022 at 01:20:15PM +0200, Martin Husemann wrote:
> On Sun, Jul 03, 2022 at 05:21:27AM -0000, Michael van Elst wrote:
> > Another question of course is why the isa fd driver reads a disklabel at all
> > when it (ab-)uses the partition number to select densities.
&g
j...@ziaspace.com (John Klos) writes:
>boot device: fd0 [ 5.121888] fd0d: hard error reading fsbn 0 of 0-2 (st0
>0x40 st1 0x1 st2 0x0 cyl 0 head 0 sec 1)
>She wondered why fd0d is being used here. I can't imagine this is due to
>scanning for a disklabel, since they've been around forever, so
s...@stix.id.au (Paul Ripke) writes:
>I guess I'm a little surprised by this error?
>Nor does read(2) list EROFS as a possible return, which seems sensible.
The errors listed with system calls are rarely complete, in particular for
errors you rarely observe or here for operations on something
h...@netbsd.org (Havard Eidnes) writes:
>1) Could the if_iwn driver fall back to using the 6000g2a-5 microcode
> without any code changes? (My gut feeling says "yes", but I have
> no existence proof of that.)
The only change that happened was the update of the firmware blob.
But there is no
b...@softjar.se (Johnny Billquist) writes:
>> They might be the reason for the memory shortage. You can prefer large
>> processes as victims or protect system services to keep the system
>> managable.
>So when one process tries to grow, you'd kill a process that currently
>have no issues in
b...@softjar.se (Johnny Billquist) writes:
>I don't see any realistic way of doing anything with that.
>It's basically the first process that tries to allocate another page
>when there are no more. There are no other processes at that moment in
>time that have the problem, so why should any of
c...@chuq.com (Chuck Silvers) writes:
> - fsck will take a new option "-c ea" to specify that an existing UFS2
> file system should be converted to support extended attributes
> (ie. converted to UFS2ea). This conversion first clears all of the on-disk
> pointers to extended attribute
m...@netbsd.org (Emmanuel Dreyfus) writes:
>On Thu, May 12, 2022 at 07:26:58AM +0200, Michael van Elst wrote:
>> This seems to suggest that we have special codes on the JIS keyboard
>> for:
>>
>> Yen 0x5d (KC_JPY ?)
>> Ro0x5e (KC_RO ?)
>> Eisu
codes on the JIS keyboard
for:
Yen 0x5d (KC_JPY ?)
Ro0x5e (KC_RO ?)
Eisu 0x66 (Switch to Roman)
Kana 0x68 (Switch to Hiragana)
, 0x5f (numeric keypad)
Greetings,
--
Michael van Elst
Internet: mlel...@serp
m...@netbsd.org (Emmanuel Dreyfus) writes:
>It seems the layout can be detected using sc->sc_adbdev->handler_id
>I borrowed the values from tmk_keyboard and it works fine. There
>are just a few numerical values for which I have no name. Where is the
>ADB keyboard handler id name list?
I found
m...@netbsd.org (Emmanuel Dreyfus) writes:
>The french ADB keyboard features a < key at the right of the left shift
>key. On the console it works fine, however with X, it displays a @. The
>@ key also displays a @.
Apparently there are two different encodings for ANSI and ISO keyboard
layouts
mlel...@serpens.de (Michael van Elst) writes:
>- The copied filesystem code in libsa uses absolute disk offsets
> in bytes to locate superblocks. A backend that uses physical blocks
> cannot easily address such offsets if it doesn't know the block
> size.
> The filesyst
nick.hud...@gmx.co.uk (Nick Hudson) writes:
>https://github.com/skrll/src/commit/a5432c0ce71ea2fd1b7ad22ff6c26d01f4dca7=
>1a
When looking at this, I got a few more issues:
- The copied filesystem code in libsa uses absolute disk offsets
in bytes to locate superblocks. A backend that uses
nick.hud...@gmx.co.uk (Nick Hudson) writes:
>To enable efiboot to work from Apple M1 nvme I had to apply this diff so
>that libsa picks up the fs_fshift based FFS_FSBTODB.
>Is this correct or does it mean the FS has an incorrect fs_fsbtodb? (and
>there's a bug in mkfs somewhere)
The bug is
On Mon, Apr 11, 2022 at 04:23:04PM -0700, Paul Goyette wrote:
> On Mon, 11 Apr 2022, RVP wrote:
>
> > On Mon, 11 Apr 2022, Michael van Elst wrote:
> >
> > > N.B. if the display driver provides EDID data to wscons it can be
> > > queried with
> > >
&
On Tue, Apr 12, 2022 at 12:52:36AM +, Emmanuel Dreyfus wrote:
> On Mon, Apr 11, 2022 at 11:37:29AM -0000, Michael van Elst wrote:
> > I rather doubt that a black display comes from the refresh rate.
>
> In X11, I get it working at 50 Hz, but I get a black display at 60
m...@netbsd.org (Emmanuel Dreyfus) writes:
>When the kernel initialize a framebuffer, the signal ouput changes a bit
>fro mwhat is inherited from the BIOS. I face the situation where the
>display looses the signal, and I suspect this is related to the refresh
>rate.
BIOS usually sets fixed
dty...@anduin.org.uk (Dave Tyson) writes:
>The contents of the dtb shoved in-core can be modified by having code snippets
>in the overlay directory and enabling them in config.txt. This is how bullseye
>linux seems to do things and I guess this should work with NetBSD.
Yes, works the same.
campbell+netbsd-tech-k...@mumble.net (Taylor R Campbell) writes:
>I think usually it's first-come-first-serve according to the ordering
>in the device tree (that is, in a pre-order traversal, which is the
>same as the sequential order in the .dts file) -- not necessarily the
>numbers in the
b...@softjar.se (Johnny Billquist) writes:
>Which then basically means that without MAP_FIXED, the hint don't really
>mean anything? It will take whatever address it can come up with, no
>matter what you put into the hint.
It still might reuse the address (or just a close address) for
p...@cielonegro.org (PHO) writes:
>I expected mmap(2) to search for an available region from the entire
>address space starting from the hint, not only half of it.
It's not even half.
b...@softjar.se (Johnny Billquist) writes:
>If it would ignore the hint, what's the point of the hint then?
With MAP_FIXED it must use the hint, without it's just a best effort
attempt.
m...@eterna.com.au (matthew green) writes:
>while rebooting a quartz64 with a usb attached disk that just
>had a about 3.5GB of data written to it, i the umass gave some
>errorse and then i got a panic shortly later:
>[ 6179.6038961] Skipping crash dump on recursive panic
>[ 6179.6038961] panic:
m...@eterna.com.au (matthew green) writes:
>it seems to me that if some driver depends upon altq, then
>altq should simply always refuse to unload if a driver is
>loaded that depends upon it. this should be an explicit
>dependency, and probably implicit via symbols.
>if, say there's a fully
r...@sdf.org (RVP) writes:
>Are block and dk* (wedge) devices supposed to support lseek()?
When a disk device is opened, the DIOCGPARTINFO ioctl is used to
query the size of the disk and cache it in the vnode.
The dk driver doesn't represent a disk and doesn't support DIOCGPARTINFO.
It does
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
r...@sdf.org (RVP) writes:
>The kernel currently defines the backspace key as:
>$ fgrep CERASE /usr/include/sys/ttydefaults.h
>#define CERASE 0177
There is no 'defined as', in particular with emulated terminals
that aren't even the same on all platforms.
If you restrict yourself to PC
thor...@me.com (Jason Thorpe) writes:
>Well, ultimately, we translate =E2=80=9CHID report=E2=80=9D -> =E2=80=9Cws=
>* input event=E2=80=9D. Or are you suggesting that we should have a new =
>interface to user-space that just sends HID reports?
We already have a user-space interface that sends
thor...@me.com (Jason Thorpe) writes:
>Trying to think about the best way to represent such a device, I guess =
>within wscons (they almost seem sort of like a 1-axis mouse, but I could =
>be convinced otherwise).
You can make it a HID, because that's what it is.
Currently we only expose USB
On Mon, Aug 16, 2021 at 06:46:17AM -0700, Jason Thorpe wrote:
>
> > On Aug 16, 2021, at 2:31 AM, Michael van Elst wrote:
> > Isn't that what we do today? Have a common name and value format,
> > copied/translated from various sources and stored in the MI device
> &g
j...@coris.org.uk (Julian Coleman) writes:
>We can decide on the name that we'll use (e.g. `ethernet_address') and
>use that in all the drivers.
Isn't that what we do today? Have a common name and value format,
copied/translated from various sources and stored in the MI device
dictionary.
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
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
mueller6...@twc.com ("Thomas Mueller") writes:
>Where do I find the "enough dk* nodes" mode? Would it be in the kernel
>config? I never saw it.
You can run devpubd. When a wedge and thus the dk* unit attaches, it
runs the 01-makedev hook that creates the device node in /dev.
mueller6...@twc.com ("Thomas Mueller") writes:
>It's a nuisance not to be able to recognize all partitions on a
>GPT-partitioned drive because not enough dk* nodes have been configured.
>FreeBSD even distinguishes between USB or SCSI disks and SATA disks, and
>between GPT partitions and
dholland-t...@netbsd.org (David Holland) writes:
>This was all based on the experience of adding discard and adding the
>dispatching for it as a first-class [bc]devsw op rather than an ioctl:
>it was a pain because it ultimately required touching _every_ driver,
>not just the ones that needed to
etings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mlel...@serpens.de (Michael van Elst) writes:
>Either direction mstohz or hztoms should better always round up to
>guarantee a minimal delay.
And both should be replaced by hztous()/ustohz().
Microseconds allow a time value of ~35 minutes as 32bit signed
integer, which should be a safe
1 - 100 of 469 matches
Mail list logo
