I guessing here, but I believe the /proc/gpio interface you’re referring to was exposed on a different class of gumstix boards (the verdex perhaps?). Many of the gpio lines in the Overo kernel are exposed in sysfs at /sys/class/gpio
I believe that GPIO 164 is tied to the Bluetooth reset if that’s what you were looking for. However, in the case that you have a working Bluetooth I think it should just come up operational when hciattach runs.
Frankly, I saw that post. I though I do another post and see if anything new was up. The thing that worried me is that there is no /proc/gpio in the image I built, neither on the ready images and I was thinking whether this is related to the bluetooth issue. Does anyone know whether there should be a /proc/gpio? I do not have the proc_gpio module either to load.
I will be getting 5-6 more, so I will be able to see if indeed it is a bad board. At the moment I am waiting because there is no stock.
From: Thad Thompson <TThompson@Nucsafe.com>
To: General mailing list for gumstix users. <firstname.lastname@example.org>
Sent: Friday, July 3, 2009 7:12:33 PM
Subject: Re: [Gumstix-users] Overo Fire bluetooth not working
If you check the mailing list archives you’ll find this is an issue a few of us have been dealing with, but it seems to only happen on a few boards. At this point in time I think the only solution is to RMA the board and try again.
I have an overo Fire on a Summit expansion board.
Bluetooth fails with the following message:
Starting Bluetooth subsystem:
Initialization timed out.
This happened with the image the module came with. I tried building an image, as well as using latest images but the same happened with all of them.
In the users WiKi How-To: Bluettoth it mentions GPIOs. I noticed that there is no /proc/gpio. I am not sure whether this has to do with the bluetooth failure or if it is another problem.
Any help is welcomed!