Adding GPIO support to wbsio(4)

2018-11-03 Thread Matt Dainty
Attached below is a diff that adds GPIO support to wbsio(4) for the Nuvoton NCT5104D variant which is found on most of the recent PC Engines APU boards, (I'm personally developing this on an APU4). I've hit a problem that it causes the kernel to crash when probing for lm78(4) which can be found

Re: Implement a watchdog

2014-12-11 Thread Matt Dainty
* sven falempin sven.falem...@gmail.com [2014-12-10 12:32:15]: On Wed, Dec 10, 2014 at 9:31 AM, Stuart Henderson st...@openbsd.org wrote: On 2014/12/10 09:15, sven falempin wrote: http://lxr.free-electrons.com/source/drivers/hwmon/nct6775.c https://github.com/groeck/nct6775 So i guess

Re: Soekris net6501 GPIO LED support

2014-12-09 Thread Matt Dainty
* Ted Unangst t...@tedunangst.com [2014-12-08 13:28:36]: On Mon, Dec 08, 2014 at 11:52, Matt Dainty wrote: * Jonathan Gray j...@jsg.id.au [2014-12-08 08:08:19]: Well any name that includes gpio that isn't taken should be fine. I went with soekrisgpio(4) as there are longer driver names

Re: Soekris net6501 GPIO LED support

2014-12-08 Thread Matt Dainty
- @@ -0,0 +1,57 @@ +.\ $OpenBSD$ +.\ +.\ Copyright (c) 2014 Matt Dainty m...@bodgit-n-scarper.com +.\ +.\ Permission to use, copy, modify, and distribute this software for any +.\ purpose with or without fee is hereby granted, provided that the above +.\ copyright notice and this permission

Re: Soekris net6501 GPIO LED support

2014-12-05 Thread Matt Dainty
Anyone? * Matt Dainty m...@bodgit-n-scarper.com [2014-11-21 07:10:24]: * Dimitri Sokolyuk de...@dim13.org [2014-11-05 22:05:26]: I would also like to ask, if there are any plans on reviewing and committing this code into base? Here's an updated patch with the driver and associated man

Re: Soekris net6501 GPIO LED support

2014-12-05 Thread Matt Dainty
or suggestions? I wonder if the 16 bit general purpose I/O, 26 pins header, connected to FPGA on the net6801 will have the same interface. I saw this too. Without seeing any details my hunch is it will probably be very similar. Matt On Fri, Dec 05, 2014 at 10:05:46AM -0500, Matt Dainty wrote

Re: Soekris net6501 GPIO LED support

2013-03-13 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2013-01-14 11:13:59]: Attached is a patch that adds soekris(4) which provides access to the GPIO and LEDs as implemented by the onboard Xilinx FPGA on the Soekris net6501. The driver provides two GPIO buses; one for the 16 real GPIO pins exposed

Re: Soekris net6501 GPIO LED support

2013-03-13 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2013-03-13 07:56:14]: I'll send a separate patch with the various man page changes. And here's the man page changes. Matt --- /dev/null Wed Mar 13 10:31:11 2013 +++ share/man/man4/man4.amd64/soekris.4 Tue Feb 19 08:34:54 2013 @@ -0,0 +1,57

Re: Add Soekris comBIOS detection to bios(4) on i386/amd64

2013-03-12 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2013-02-20 19:30:43]: Attached are two patches for bios(4) on i386 amd64 that add support for detecting the comBIOS on Soekris hardware, which then fills in the hw.vendor hw.product sysctl variables as this hardware lacks any SMBIOS to provide them

Re: Add Soekris comBIOS detection to bios(4) on i386/amd64

2013-03-12 Thread Matt Dainty
* Kenneth R Westerback kwesterb...@rogers.com [2013-03-12 06:39:02]: On Tue, Mar 12, 2013 at 05:13:01AM -0400, Matt Dainty wrote: * Matt Dainty m...@bodgit-n-scarper.com [2013-02-20 19:30:43]: Attached are two patches for bios(4) on i386 amd64 that add support for detecting the comBIOS

Re: Add Soekris comBIOS detection to bios(4) on i386/amd64

2013-03-04 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2013-02-20 19:30:43]: Attached are two patches for bios(4) on i386 amd64 that add support for detecting the comBIOS on Soekris hardware, which then fills in the hw.vendor hw.product sysctl variables as this hardware lacks any SMBIOS to provide them

Add Soekris comBIOS detection to bios(4) on i386/amd64

2013-02-20 Thread Matt Dainty
Attached are two patches for bios(4) on i386 amd64 that add support for detecting the comBIOS on Soekris hardware, which then fills in the hw.vendor hw.product sysctl variables as this hardware lacks any SMBIOS to provide them. The idea is then these can be used in the GPIO/LED driver for the

Re: Detect on-die temp sensor for Atom E6xx on amd64

2013-01-30 Thread Matt Dainty
* Mark Kettenis mark.kette...@xs4all.nl [2013-01-30 03:49:45]: Date: Tue, 29 Jan 2013 17:35:13 -0500 From: Matt Dainty m...@bodgit-n-scarper.com * Christian Weisgerber na...@mips.inka.de [2013-01-24 13:03:43]: Matt Dainty m...@bodgit-n-scarper.com wrote: --- sys/arch/amd64

Re: Detect on-die temp sensor for Atom E6xx on amd64

2013-01-29 Thread Matt Dainty
* Christian Weisgerber na...@mips.inka.de [2013-01-24 13:03:43]: Matt Dainty m...@bodgit-n-scarper.com wrote: --- sys/arch/amd64/amd64/identcpu.c.orig2013-01-14 22:23:43.0 + +++ sys/arch/amd64/amd64/identcpu.c 2013-01-14 22:33:21.0 + @@ -506,7 +506,8

Soekris net6501 GPIO LED support

2013-01-14 Thread Matt Dainty
on the GPIO pins. Comments? Matt --- /dev/null Tue Jan 8 21:22:57 2013 +++ sys/dev/isa/soekris.c Tue Jan 8 21:17:02 2013 @@ -0,0 +1,235 @@ +/* $OpenBSD$ */ + +/* + * Copyright (c) 2013 Matt Dainty m...@bodgit-n-scarper.com + * + * Permission to use, copy, modify, and distribute

Detect on-die temp sensor for Atom E6xx on amd64

2013-01-14 Thread Matt Dainty
The following patch fixes the the detection of the on-die temp sensor for Atom E6xx CPUs (and possibly other Atom CPUs). The code was only matching processors where the model began with Intel but this Atom CPU model begins with Genuine Intel so I've updated the logic to match. Now I get: #

Re: Add HPET support to tcpcib(4)

2012-06-04 Thread Matt Dainty
* Mark Kettenis mark.kette...@xs4all.nl [2012-06-03 08:51:03]: Date: Sat, 2 Jun 2012 15:36:22 -0400 From: Matt Dainty m...@bodgit-n-scarper.com As before but with the verbosity of the attach line tuned down a notch and not printing extra ':'s as pointed out by Theo. So now it looks

Add HPET support to tcpcib(4)

2012-06-02 Thread Matt Dainty
Attached are some patches that update the recently added tcpcib(4) driver with support for using the HPET as a timecounter, based on amdpcib(4). Here's the updated dmesg: ---8--- tcpcib0 at pci0 dev 31 function 0 Intel E600 LPC rev 0x00: 64-bit 14318179 Hz timer rev 1: watchdog ---8--- Here's

Re: Intel Atom E600 watchdog(4) support

2012-05-25 Thread Matt Dainty
) 2012 Matt Dainty m...@bodgit-n-scarper.com + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED

Re: Intel Atom E600 watchdog(4) support

2012-05-24 Thread Matt Dainty
with i386. Thanks, much appreciated. Updated patch below. Matt --- /dev/null Thu May 24 00:43:16 2012 +++ sys/dev/pci/pchpcib.c Thu May 24 00:34:28 2012 @@ -0,0 +1,220 @@ +/* $OpenBSD$ */ + +/* + * Copyright (c) 2012 Matt Dainty m...@bodgit-n-scarper.com + * + * Permission to use

Re: Intel Atom E600 watchdog(4) support

2012-05-24 Thread Matt Dainty
* Mitja MuEeniD mi...@muzenic.net [2012-05-24 07:23:22]: Works for me on net6501 on i386 GENERIC and GENERIC.MP after a succesfull watchdog fire: e600pcib0 at pci0 dev 31 function 0 Intel E600 LPC rev 0x00: watchdog, reboot on timeout It did fire a bit too early though, my watchdog

Intel Atom E600 watchdog(4) support

2012-05-23 Thread Matt Dainty
2012 +++ sys/dev/pci/e600pcib.c Wed May 23 21:00:44 2012 @@ -0,0 +1,220 @@ +/* $OpenBSD$ */ + +/* + * Copyright (c) 2012 Matt Dainty m...@bodgit-n-scarper.com + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted

Re: RFC 4638 support for pppoe(4)

2012-01-11 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2012-01-09 20:21:54]: * Matt Dainty m...@bodgit-n-scarper.com [2012-01-02 16:30:55]: * Stuart Henderson s...@spacehopper.org [2011-12-31 10:12:41]: If the remote side doesn't echo our tag back, we should restrict ourselves to PPPOE_MAXMTU

Re: RFC 4638 support for pppoe(4)

2012-01-09 Thread Matt Dainty
* Matt Dainty m...@bodgit-n-scarper.com [2012-01-02 16:30:55]: * Stuart Henderson s...@spacehopper.org [2011-12-31 10:12:41]: If the remote side doesn't echo our tag back, we should restrict ourselves to PPPOE_MAXMTU. Certainly until we are checking this I think we should avoid

Stop pppoe(8) server from agreeing to RFC 4638

2012-01-06 Thread Matt Dainty
While trying to test my RFC 4638 changes for pppoe(4) against a PPPoE server that won't agree to the increased MTU, I found that after setting up a pppoe(8)-based server I wasn't getting the expected behaviour. It turns out pppoe(8) returns all of the clients tags in addition to any tags specific

RFC 4638 support for pppoe(4)

2011-12-27 Thread Matt Dainty
Attached are three patches for RFC 4638 PPPoE support. The first two are for pppoe(4) based on similar changes made to NetBSD. The third patch is to tcpdump(8) so it recognises the additional tag type. I've been running this on my Soekris net6501 with one of the the built in em(4) chips hooked up