Date: Mon, 20 May 2013 18:41:49 +0100 From: Joe Holden <lists@rewt.org.uk> To: Milan Obuch <freebsd-mips@dino.sk> Cc: Aleksandr Rybalko <ray@ddteam.net>, "freebsd-mips@FreeBSD.org" <freebsd-mips@freebsd.org> Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Message-ID: <519A605D.8020304@rewt.org.uk> In-Reply-To: <20130520173934.099ea541@zeta.dino.sk> References: <CACVs6=_UHMvo6DSyXzvXxJ0eCcSsC%2Bk3yZ42ia5TGzgHduT2zA@mail.gmail.com> <20130516111059.38543d57@wind.dino.sk> <20130516131642.adfae355aa3bf7767e9b56e5@ddteam.net> <20130516124248.33ae4e05@wind.dino.sk> <51952112.9010607@rewt.org.uk> <20130517192206.5db0533f@zeta.dino.sk> <51966CB6.2040701@rewt.org.uk> <CACVs6=-0URQ2f7UqVxRdpuGpf103KOW9CTF6FFCGaGhvg3jOMw@mail.gmail.com> <20130520110659.1d1d2165@zeta.dino.sk> <D1F45DEB-3C3C-42D1-8EDE-94B18AB32152@bsdimp.com> <20130520164001.5f7d99b8@zeta.dino.sk> <C48F8AE6-316B-4C4A-AD2B-739C698B0AAC@bsdimp.com> <20130520172508.087daf7b@zeta.dino.sk> <CACVs6=8_y5Rqo9UHnQwbEancfZOqrqEAhcu=EXGGSGLjvayKVg@mail.gmail.com> <20130520173934.099ea541@zeta.dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
Milan Obuch wrote: > On Mon, 20 May 2013 08:27:40 -0700, Juli Mallett <jmallett@FreeBSD.org> > wrote: > >> On Mon, May 20, 2013 at 8:25 AM, Milan Obuch <freebsd-mips@dino.sk> >> wrote: >>> Yes, output is from 'gpioctl -f /dev/gpioc0 -lv' command execution. >>> Actually, I wrote all 16 pins (0 to 15) in >>> sys/mips/cavium/octeon_gpio.c so I can see quickly which GPIO pin >>> is connected to reset switch. Pin 11 changed when pressing the >>> switch. >> Could you try commenting out everything but pin 11 in octeon_gpio.c >> and rebuilding? I'm wondering if one of those pins may have been >> in-use to talk to some Ethernet hardware or something like that, and >> that its operation was disrupted by the GPIO driver. > > As far as I know, it behaved this way even before I added those pin > definition into GPIO driver. Actually, full output is > > gpioctl -f /dev/gpioc0 -lv > pin 00: 0 F/D0<IN>, caps:<IN,OUT> > pin 01: 0 F/D1<IN>, caps:<IN,OUT> > pin 02: 0 F/D2<IN>, caps:<IN,OUT> > pin 03: 0 F/D3<IN>, caps:<IN,OUT> > pin 04: 0 F/D4<IN>, caps:<IN,OUT> > pin 05: 0 F/D5<IN>, caps:<IN,OUT> > pin 06: 0 F/D6<IN>, caps:<IN,OUT> > pin 07: 0 F/D7<IN>, caps:<IN,OUT> > pin 08: 1 F/D8<IN>, caps:<IN,OUT> > pin 09: 1 F/D9<IN>, caps:<IN,OUT> > pin 10: 1 F/D10<IN>, caps:<IN,OUT> > pin 11: 1 F/D11<IN>, caps:<IN,OUT> > pin 12: 0 F/D12<IN>, caps:<IN,OUT> > pin 13: 0 F/D13<IN>, caps:<IN,OUT> > pin 14: 0 F/D14<IN>, caps:<IN,OUT> > pin 15: 0 F/D15<IN>, caps:<IN,OUT> > > and does not change with link status on ethernet port (any). But I will > test it with only pin 11 left there, just in case I overlooked > something. > > Regards, > Milan Hm, I do recall seeing something in a document somewhere that suggested it used gpio/i2c to talk to the PHYs due to the design they've used, is there any way of dumping accesses/messages across gpio pins (without soldering) ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?519A605D.8020304>