Date: Fri, 17 May 2013 19:22:06 +0200 From: Milan Obuch <freebsd-mips@dino.sk> To: Joe Holden <lists@rewt.org.uk> Cc: Aleksandr Rybalko <ray@ddteam.net>, freebsd-mips@freebsd.org Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Message-ID: <20130517192206.5db0533f@zeta.dino.sk> In-Reply-To: <51952112.9010607@rewt.org.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 May 2013 19:10:26 +0100, Joe Holden <lists@rewt.org.uk> wrote: [ snip ] > > for this quick test I used OCTEON1 kernel config with some necessary > > tweaks, device gpio is commented out, maybe this will be enough for > > enable octeon_gpio.c (looking at files.octeon1 it seems to be > > possible). I will test it, definitely. > > There is only one pin exposed via gpio: > > root@erl1:~ # gpioctl -f /dev/gpioc0 -l -v > pin 07: 0 F/D<IN>, caps:<IN,OUT> > > Not sure if it maps to anything usable, haven't played with it yet - > the other header is EJTAG according to Cavium docs. I built new kernel with device gpio, something is not working - F/D should mean 'factory default' aka 'reset switch', but it does not sense status ot that switch. No matter whether pressed or not, gpioctl still reports 0. Also, somehow strangely, in dmesg: gpio0: <Cavium Octeon GPIO driver> on ciu0 gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [GIANT-LOCKED] gpio0: [pin0] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin1] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin2] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin3] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin4] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin5] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin6] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin7] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin8] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin9] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin10] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin11] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin12] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin13] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin14] output=0, invinput=0, intr=0, intr_type=level gpio0: [pin15] output=0, invinput=0, intr=0, intr_type=level gpioc0: <GPIO controller> on gpio0 gpiobus0: <GPIO bus> on gpio0 GIANT-LOCKED line is there 16 times, once for every one from 16 pins - why? Regards, Milan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130517192206.5db0533f>