Re: Intel Atom E600 watchdog(4) support

2012-05-23 Thread Jonathan Gray
As a general policy drivers do not have numbers in their name, so it will have to be renamed. I'll have a look into trying it on a net6501 I have here with i386. On Wed, May 23, 2012 at 04:52:03PM -0400, Matt Dainty wrote: > Attached are some patches that add support for the watchdog device on >

Intel Atom E600 watchdog(4) support

2012-05-23 Thread Matt Dainty
Attached are some patches that add support for the watchdog device on boards based on the Intel Atom E600 series such as the Soekris net6501. Based on existing drivers such as amdpcib(4), ichpcib(4) and ichwdt(4) I've created an e600pcib(4) to override the standard pcib(4) which can then access th

Re: sparc64 gcc4/asm illegal operands, Re: CVS: cvs.openbsd.org: ports

2012-05-23 Thread Miod Vallat
> Looks like these "Illegal operands" errors from the assembler started after > the move to gcc4, the offending asm code looks like > > fdtox %f12, %f9 > fdtox %f10, %f15 > fdtox %f8, %f9 > fdtox %f12, %f7 > > Any suggestions? I have started to investigate this. This sounds like the good

Re: wpi: add sensor for rfkill

2012-05-23 Thread Gregor Best
On Thu, May 24, 2012 at 01:42:36AM +1000, Jonathan Gray wrote: > [...] > Could you explain why you have need of this sensor I don't > quite see it? > [...] I usually manage the network connections on my laptop with an ifstated configuration. If the wireless device's link went down, it could be for

Re: wpi: add sensor for rfkill

2012-05-23 Thread Jonathan Gray
On Wed, May 23, 2012 at 05:22:24PM +0200, Gregor Best wrote: > On Wed, May 23, 2012 at 09:12:20AM +0200, Tobias Ulmer wrote: > > [...] > > This a read-only sensor, it has no effect on misbehaving > > hardware as far as I can tell. > > [...] > > That is right. If I recall correctly, the very reason

Re: wpi: add sensor for rfkill

2012-05-23 Thread Gregor Best
On Wed, May 23, 2012 at 09:12:20AM +0200, Tobias Ulmer wrote: > [...] > This a read-only sensor, it has no effect on misbehaving > hardware as far as I can tell. > [...] That is right. If I recall correctly, the very reason for introducing real hardware killswitches was so that the OS could not i

fstatfs64 for compat/linux

2012-05-23 Thread Paul Irofti
Okay? Index: linux_misc.c === RCS file: /cvs/src/sys/compat/linux/linux_misc.c,v retrieving revision 1.77 diff -u -p -r1.77 linux_misc.c --- linux_misc.c23 May 2012 11:08:57 - 1.77 +++ linux_misc.c23 May 2012

Re: mg(1) start up file diffs (2 of 2)

2012-05-23 Thread Mark Lumsden
"any of the *file* commands" should be... any of the other *file* commands such as insert-file, etc.. - Forwarded message from Mark Lumsden - From: Mark Lumsden To: tech@openbsd.org Subject: mg(1) start up file diffs (2 of 2) Further to my previous email, I noticed if I tried to u

mg - start up file diffs (2 of 2)

2012-05-23 Thread Mark Lumsden
Further to my previous email, I noticed if I tried to use any of the *file* commands in the startup ~/.mg file, nothing happened. By looking at main.c, I realised that the order of starup function calls was the problem. This diff moves the creation of the startup buffers before parsing the startup

mg - start up file diffs (1 of 2)

2012-05-23 Thread Mark Lumsden
If you want to open up a file using the mg startup file (~/.mg) using the find-file command, e.g: find-file main.c mg will give an odd message of "File read error", but the file opens anyway. However, if by accident you try to open a non-existant file mg will segv. After investigating I found m

Re: wpi: add sensor for rfkill

2012-05-23 Thread Tobias Ulmer
On Wed, May 23, 2012 at 01:27:26PM +1000, Brett wrote: > On Tue, 22 May 2012 20:20:38 +0200 > Gregor Best wrote: > > > Hi people, > > > > the attached patch adds an indicator sensor to wpi devices that describes > > the > > current RFKill status. If the RF killswitch is engaged, the sensor rea