Yes. Actually, some of that you can do now (at least as far as what
userspace apps are included). You can remove the bluetooth userspace
stuff by just removing bluetooth from the TARGETS list. It still
compiles all the BT modules into the kernel build though. Having
some of the other stuff like setting up the GPIOs for ttyS2 vs ttyS3
would be nice actually. Right now, u-boot is mainly responsible for
configuring the GPIOs, but it would probably be pretty easy to write
a simple script for /etc/init.d which poked stuff into /proc/gpio to
set up stuff like this, and have that script configured by some high-
level settings in the buildroot top-level makefile. Doing it in the
Makefile though will probably rapidly get into tricky areas though,
where some features depend on others, and you can have conflicts --
eg CF versus MMC or HWUART-to-waysmall vs HWUART-to-bluetooth which
need to be resolved. The only practical way of dealing with those
sorts of things would be to have a config system similar to the one
the linux kernel uses, which passes options to the packages below.
The mainline buildroot has actually moved to a system like this --
maybe I should get around to actually migrating to their new tree
structure. I've been avoiding it for a while now, but it could be
time for that soon.
On Jul 18, 2005, at 6:21 AM, Cyril Bazin wrote:
> Now, there are tons of differents gumstix, daughter boards and for
> each couple of gumstix/motherborad there are many possibles
> It could be interesting to configure the type of configuration you
> want to use before the buildroot compilation.
> For example: bluetooth or ttyS3, preconfigured ttyS2 or not,
> configuring which of ttyS2 and ttyS3 is the second serial port, etc
> But, I think Craig is too busy for that, it's just a suggestion to
> improve the quality of the product in the future...
> On 7/17/05, Naveen Sastry <nks@...> wrote:
> yep. We were able to get the HWUART on the breakout-gs board.
> If I remember correctly, all we had to do was:
> a) run the flow control patch (r-516).
> b) set the appropriate GPIO pins to use the HWUART; by default they're
> not setup for it. I think:
> echo "AF1 out" >/proc/gpio/GPIO48
> echo "AF1 in" >/proc/gpio/GPIO49
> will do it (from memory). There's a post by Cyril on the mailing list
> that provided that useful tidbit. We tested it with wermit and were
> to conenct to another serial running a getty.
> John Cole wrote:
> > Has anyone gotten the HWUART on the breakout-gs to work yet? I have
> > been trying for several days with no luck. I am currently
> running r-516
> > with the 201 no flow control kernel patch. Have tried every
> > I can think of, but no luck. I have verified that the data
> stream is
> > running to the pins, but seems to not be being received by the
> > Any suggestions would be much appreciated
> > John
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > gumstix-users mailing list
> > gumstix-users@...
> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> gumstix-users mailing list