Date: Mon, 17 Jun 2013 21:23:19 -0600 From: Warner Losh <imp@bsdimp.com> To: mcgovern@beta.com Cc: freebsd-arm@freebsd.org Subject: Re: Two questions on -current... Message-ID: <BD5C6503-7C00-41A1-B255-5DA80322CB31@bsdimp.com> In-Reply-To: <1371521474.1391.9.camel@fbsd-laptop> References: <mailman.57.1371470402.63030.freebsd-arm@freebsd.org> <1371521474.1391.9.camel@fbsd-laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 17, 2013, at 8:11 PM, Brian J. McGovern wrote: > I'm currently using a fairly recent (within the week) -current on a > Beaglebone Black and trying to use it on an OpenRD ultimate... I have > two questions that I can't seem to find recent answers online. >=20 > 1.) On the Beaglebone black, is there an interface for setting up the > MUX on the GPIO pins? I've seen gpioctl, which doesn't seem to have = the > capability, and there seems to be settings in the DTS file, although = it > appears incomplete (e.g. not all pins are configured), but is there a > way to dynamically set up the MUX during run time? There's only limited support for this on some ports. It is one of the = biggest holes we have today. > 2.) When trying to compile DB-88F6XXX, I'm getting an error "error: > unknown target CPU 'armv5te', despite a find ... grep... on the code > showing this option in both gcc and clang compilers and tools. Is this > processor deprecated in current? Is there are a replacement? Did I = miss > a change in how to build the kernel (Currently using "make TARGET=3Darm > TARGET_ARCH=3Darm KERNCONF=3DDB-88F6XXX buildkernel" in /usr/src)? Do you have TARGET_CPU set somewhere? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD5C6503-7C00-41A1-B255-5DA80322CB31>