Re: thousands of callout_cpu0

2015-11-24 Thread Frank Wille
is usable from crash(8). >Is that the change that broke it? Can you revert kern_timeout.c and >see if that fixes it? Yes, confirmed. That's the problem! Going back to 1.48 fixes it! Regards, -- Frank Wille

thousands of callout_cpu0

2015-11-23 Thread Frank Wille
ere? -- Frank Wille

Re: Removing ARCNET stuffs

2015-05-27 Thread Frank Wille
iga users if anybody owns such a board. Probably is@ still got one, as he was working on the driver many years ago. When nothing happens and nobody is able to test it, we can remove the code. -- Frank Wille

Re: Removing ARCNET stuffs

2015-05-27 Thread Frank Wille
be irrelevant for the Amiga platform? -- Frank Wille

Re: Removing ARCNET stuffs

2015-05-27 Thread Frank Wille
an Arcnet board he would be happy to use it. What are the reasons behind removing working parts from the source tree anyway? Aren't there more important things to do? -- Frank Wille

Re: re(4) MAC address

2012-12-28 Thread Frank Wille
tk_setmulti' As this is the only function needed from rtl81x9.c it probably makes sense to add rtk_setmulti() and the rtk_calchash macro to rtl8169.c. I tried that and it works fine with my NAS! New patch for rtl8169.c, including re_setmulti(), is attached. -- Frank Wille rtl8169.c.diff Description: Binary data

Re: re(4) MAC address

2012-12-02 Thread Frank Wille
ses default values when the EEPROM is missing. -- Frank Wille

Re: re(4) MAC address

2012-12-01 Thread Frank Wille
calls (like sys/dev/pci/if_wm.c etc). Yes. I added a mac-address property to sk(4) myself, some time ago. But re(4) doesn't support it yet. -- Frank Wille

re(4) MAC address

2012-12-01 Thread Frank Wille
0 Ethernet (0x8169) [...] Sorry for cross-posting, but I couldn't decide whether this belongs to tech-kern or tech-net. -- Frank Wille

Re: kmem change related trouble

2012-02-03 Thread Frank Wille
uvm_km.txt) helps! I need some more testing, but most kernel functions seem normal again. Thanks. -- Frank Wille

Re: kmem change related trouble

2012-02-03 Thread Frank Wille
t; kmem_intr_alloc > > exec_elf32_makecmds > > check_exec > > execve1 > > start_init, > > setfunc_trampoline > > is that with the latest exec_elf.c? No. It was still 1.33. > I'd like to see if the location changes with the latest one. Ok. I will test an updated kernel this evening. -- Frank Wille

Re: kmem change related trouble

2012-02-02 Thread Frank Wille
0xa00011c8 by pool_cache_get_paddr+0x4c: srr1=0x9032 r1=0xa22b9aa0 cr=0x28284084 xer=0x02000 ctr=0x1642c dsisr=0x4000 The backtrace: copyright kmem_intr_alloc exec_elf32_makecmds check_exec execve1 start_init, setfunc_trampoline -- Frank Wille

Re: VT6410 IDE and WDC_NO_IDS

2012-01-04 Thread Frank Wille
g an edge-triggered PCI interrupt seems to solve the problem for me. If anybody can test a VT6410 on a different platform, I would be interested in the results. -- Frank Wille

Re: VT6410 IDE and WDC_NO_IDS

2011-12-28 Thread Frank Wille
ation now, because I found a better solution: on the MPC8241 I can configure the VT6410 PCI interrupt as edge-triggered. That cures the problem completely. It needs to be checked if other architectures have the same problem with the VT6410. -- Frank Wille

VT6410 IDE and WDC_NO_IDS

2011-12-25 Thread Frank Wille
ch I would have to change too. Would that be ok for everybody? Or is there a better solution? -- Frank Wille

Re: pci_mapreg_map() with disabled device

2011-12-01 Thread Frank Wille
On Thu, 1 Dec 2011 13:06:33 + "Jonathan A. Kollasch" wrote: > On Thu, Dec 01, 2011 at 10:12:44AM +0100, Frank Wille wrote: > > Is there a reason why pci_mapreg_map() calls bus_space_map() for a > > memory or i/o space, even when all spaces have been disabled on

pci_mapreg_map() with disabled device

2011-12-01 Thread Frank Wille
0xf3ff) extent_alloc_region: start 0x0, end 0xfff panic: extent_alloc_region: region lies outside extent Wouldn't it be better to check whether a space is enabled in the device, before trying to map it? -- Frank Wille

Re: 32-bit partition offset/size in disklabel

2011-11-30 Thread Frank Wille
On Wed, 30 Nov 2011 11:56:26 +0100 Martin Husemann wrote: > On Wed, Nov 30, 2011 at 11:49:46AM +0100, Frank Wille wrote: > > Hmm... that means I would have to make a small boot/root partition, > > which uses dkctl(8) to make the rest of the disk available? > > Depends on w

Re: 32-bit partition offset/size in disklabel

2011-11-30 Thread Frank Wille
ported by sysinst? And what about other partition formats, like Apple Partition Maps, Amiga RDB, SGI, Sparc...? Is it planned to add support for them? -- Frank Wille

32-bit partition offset/size in disklabel

2011-11-30 Thread Frank Wille
p_offset; /* starting sector */ [...] I don't understand how NetBSD supports partitions larger than 2TB or starting beyond the 2TB boundary (assuming a sector size of 512 bytes)... -- Frank Wille

Re: kernel bitreverse function

2011-04-04 Thread Frank Wille
ograms, but for the kernel it makes no sense to use them, because: 1. They are inline functions, which do not save any space. 2. They cannot easily be replaced by MD instructions. -- Frank Wille

Re: kernel bitreverse function

2011-04-03 Thread Frank Wille
o be restricted to the kernel. -- Frank Wille

Re: kernel bitreverse function

2011-04-03 Thread Frank Wille
the standard NetBSD header? Any comments? Then please speak now. :) -- Frank Wille

Re: kernel bitreverse function

2011-04-03 Thread Frank Wille
rdware instruction > (and then do it in 1 clock!) Indeed some CPUs can do that. I know that the ColdFire has a bitrev instruction. Such code can go into libkern/arch. -- Frank Wille

kernel bitreverse function

2011-04-02 Thread Frank Wille
verse functions. And I ask, because I need one too, for a new I2C driver. -- Frank Wille

Re: _KMEMUSER and __HAVE_CPU_DATA_FIRST

2010-12-25 Thread Frank Wille
r: dereferencing pointer to incomplete type /home/frank/netbsd/current/src/usr.bin/vmstat/vmstat.c:980: error: storage size of 'tci' isn't known cc1: warnings being treated as errors /home/frank/netbsd/current/src/usr.bin/vmstat/vmstat.c:980: warning: unused variable 'tci' *** Failed target: vmstat.o -- Frank Wille

Re: _KMEMUSER and __HAVE_CPU_DATA_FIRST

2010-12-24 Thread Frank Wille
+#if defined(_KERNEL) +/* + * Exported definitions unique to amiga/68k cpu support. + */ #defineM68K_MMU_MOTOROLA extern volatile unsigned int interrupt_depth; Should I commit that and fix other m68k-ports accordingly, or should I wait for a better solution? -- Frank Wille

_KMEMUSER and __HAVE_CPU_DATA_FIRST

2010-12-23 Thread Frank Wille
en _KMEMUSER is defined? I already tried to fix powerpc/include/cpu.h, but it seems that all ports are affected...? Probably I'm just confused and missing some information? ;) -- Frank Wille

Re: New apple keymap variant or keymap in /usr/share/wscons/keymaps?

2010-11-28 Thread Frank Wille
Frank Wille wrote: > I have a few additional command keys for USB keyboards used internally > in Apple notebooks, which are valid for all national layouts: > > KC(209), KS_Cmd,KS_Cmd_BrightnessDown, > KC(210), KS_Cmd,KS_Cmd_BrightnessU

chopped hid protocols in interrupts

2010-11-28 Thread Frank Wille
ing I can do about it? It has probably something to do with USBD_SHORT_XFER_OK? -- Frank Wille

New apple keymap variant or keymap in /usr/share/wscons/keymaps?

2010-11-28 Thread Frank Wille
apple") to ukbdmap.c, or just make a new keymap file in /usr/share/wscons/keymaps, which can be used wscons.cfg? -- Frank Wille

Re: Enhancing ukbd for Apple notebooks

2010-11-28 Thread Frank Wille
man keyboard, to produce a \, you have to release FN before typing ß, because this key is also part of the keypad, which is activated by FN. But it's better than nothing, and everybody can change wscons.cfg to use his favourite key for AltGr... -- Frank Wille

Re: Enhancing ukbd for Apple notebooks

2010-11-27 Thread Frank Wille
On Sat, 27 Nov 2010 19:32:22 +0100 Piotr Adamus wrote: > what about Fn-Esc as Delete key? Fn-Esc? Fn-Backspace is translated into a Delete key. > And FN-Down-Up as PgUp PgDn? Is it going it work? Yes. All that will work with my patch. -- Frank Wille

Re: Enhancing ukbd for Apple notebooks

2010-11-27 Thread Frank Wille
Frank Wille wrote: > Still we have no AltGr on Apple notebooks with just a left Alt. > Should ukbd.c, or even wskbd.c be hacked to treat Ctrl-Alt as AltGr? Hmm... Ctrl-Alt is nonsense, of course. Because it is already used as a command modifier in wscons (switch screens with functions ke

Re: Enhancing ukbd for Apple notebooks

2010-11-27 Thread Frank Wille
wskbd.c be hacked to treat Ctrl-Alt as AltGr? Although I wouldn't like it to press three keys at once, just for a \ or [. -- Frank Wille

Re: Enhancing ukbd for Apple notebooks

2010-11-27 Thread Frank Wille
he problem on Apple notebook keyboards, where you only have the left Alt key, remains: Where is the AltGr key? Without that key all users of non-US keymaps won't be able to type important characters like |, \, @, [, {, ~. A solution must be found. -- Frank Wille

Re: Enhancing ukbd for Apple notebooks

2010-11-26 Thread Frank Wille
under NetBSD (which is used in various X11-based GUIs). The Apple/Command keys, on the other hand, are not needed. > As an option, maybe, for those who bought the > machine for the hardware. But not as a default. Hmm... I'm unsure what to do. Maybe there is a third or fourth opinion? -- Frank Wille

Enhancing ukbd for Apple notebooks

2010-11-26 Thread Frank Wille
N. They are used to control display brightness, volume and keyboard illumination. But as I understand it cannot easily be done, as a wscons Cmd_xxx code always requires CTRL+ALT to be pressed, and not FN... -- Frank Wille

Re: kthread with kpause or callout

2010-02-22 Thread Frank Wille
n in private and I guess it will have the effect that a process or softint holding the mutex will lock out any IPL_VM interrupt during this time? -- Frank Wille

Re: kthread with kpause or callout

2010-02-08 Thread Frank Wille
you confused me! :) A callout is executed as a softint, isn't it? -- Frank Wille

Re: kthread with kpause or callout

2010-02-08 Thread Frank Wille
On Mon, 8 Feb 2010 15:09:55 +0100 Martin Husemann wrote: > On Mon, Feb 08, 2010 at 03:04:07PM +0100, Frank Wille wrote: > > [...] May I acquire this mutex during a callout (which is a > > softint, as I understand)? Will the softint sleep or busy-wait? > > Depends on the mut

Re: kthread with kpause or callout

2010-02-08 Thread Frank Wille
On Mon, 8 Feb 2010 11:29:51 +0100 Martin Husemann wrote: > On Mon, Feb 08, 2010 at 11:11:04AM +0100, Frank Wille wrote: > > - Running a kthread and calling kpause() between the polls. > > - Using a callout which reschedules itself after the poll. > > The thread is quite a

kthread with kpause or callout

2010-02-08 Thread Frank Wille
r the poll. Or is there something even better suited, which I'm missing? -- Frank Wille

Re: Catweasel driver

2010-02-06 Thread Frank Wille
mware images which could be loaded at boot and then the > memory released. Plus it keeps a single consistent API. > > Just a thought :) Sounds like a great idea to me. All the space for firmwares in the kernel, would no longer be wasted. -- Frank Wille

Re: Catweasel driver

2010-02-06 Thread Frank Wille
m to load from? Back to /dev/joy again. When I want the device to be used from another file as well, could I change the entry in the majors.xxx file into: device-majorjoy char 26 joy | myname ? -- Frank Wille

Re: Catweasel driver

2010-02-06 Thread Frank Wille
he firmware this would be impossible. -- Frank Wille

Catweasel driver

2010-02-06 Thread Frank Wille
.) 2. The card also supports two (Amiga/Atari-style) digital joysticks. It would be nice to make them appear as joy(4). Is it possible to use the same device major number as /dev/joy* but with a another driver than src/dev/ic/joy.c? -- Frank Wille

Re: ddb write and io memory

2010-01-30 Thread Frank Wille
matthew green wrote: > another alternative would be to add a flag to write, eg "write/n". True. But you would also need the size, e.g. "write/nb". I think about it... -- Frank Wille

Re: ddb write and io memory

2010-01-30 Thread Frank Wille
matthew green wrote: >On Sat, Jan 30, 2010 at 08:45:48PM +0100, Frank Wille wrote: >> Therefore I would like to change ddb/db_write_cmd.c as in the >>following ch: >> [...] >> >> Any objections? Do we absolutely need to print the old value here? >

ddb write and io memory

2010-01-30 Thread Frank Wille
tf("%s\n", db_num_to_str(new_value)); + db_printf("\t\t= %s\n", db_num_to_str(new_value)); db_put_value(addr, size, new_value); addr += size; Any objections? Do we absolutely need to print the old value here? -- Frank Wille