Date: Fri, 17 May 2013 13:28:06 -0400 From: Warner Losh <imp@bsdimp.com> To: Milan Obuch <freebsd-mips@dino.sk> Cc: Aleksandr Rybalko <ray@ddteam.net>, freebsd-mips@freebsd.org Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Message-ID: <634DB99C-2102-44AE-8BFD-D8D767993A13@bsdimp.com> In-Reply-To: <20130517192206.5db0533f@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 17, 2013, at 1:22 PM, Milan Obuch wrote: > On Thu, 16 May 2013 19:10:26 +0100, Joe Holden <lists@rewt.org.uk> > wrote: >=20 > [ snip ] >=20 >>> 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. >>=20 >> There is only one pin exposed via gpio: >>=20 >> root@erl1:~ # gpioctl -f /dev/gpioc0 -l -v >> pin 07: 0 F/D<IN>, caps:<IN,OUT> >>=20 >> Not sure if it maps to anything usable, haven't played with it yet - >> the other header is EJTAG according to Cavium docs. >=20 > 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. >=20 > Also, somehow strangely, in dmesg: >=20 > 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=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin1] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin2] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin3] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin4] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin5] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin6] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin7] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin8] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin9] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin10] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin11] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin12] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin13] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin14] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpio0: [pin15] output=3D0, invinput=3D0, intr=3D0, intr_type=3Dlevel > gpioc0: <GPIO controller> on gpio0 > gpiobus0: <GPIO bus> on gpio0 >=20 > GIANT-LOCKED line is there 16 times, once for every one from 16 pins - > why? Because it isn't marked as MPSAFE? Chances are something will need to be = done to make it mp safe though. Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?634DB99C-2102-44AE-8BFD-D8D767993A13>