Hi Raghu,
you should use
Because of other work, currently we are not working on that. still we need
to debug SDIO communication on hardware line.
Regards,
Dileep
On Wed, Sep 16, 2015 at 4:55 PM, wrote:
> Hi Dileep,
>
> I am also trying to bring up wl12xx based on BBB
Hi Dileep,
I am also trying to bring up wl12xx based on BBB kernel. Is there any
update on this ?
Do we need to use or & mmc3 ?
Thanks & Regard
Raghu Ramaraj
On Saturday, August 29, 2015 at 12:56:08 AM UTC+5:30, lisarden wrote:
>
> Enable dummy regulators in the kernel
> 28 Авг 2015
Hi
This is not good. You have tried to start mmc3 but it failed to get a
regulator, so may not have continued its initialisation - i don't know how
driver behaves in this case.
omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
So suggestion would be to trace omap_hsmmc driver to
Enable dummy regulators in the kernel
28 Авг 2015 г. 14:30 пользователь Iain Hunter drhunte...@gmail.com
написал:
Hi
This is not good. You have tried to start mmc3 but it failed to get a
regulator, so may not have continued its initialisation - i don't know how
driver behaves in this case.
Did you use device tree in the end or modify a board.c?
If so that looks like the mmc port is not being probed correctly as it is
not defined. You should at least get some activity on mmc to try and read
the type of sd card on this bus. This should identify as a wl12xx and
then load the drivers
Hi lain,
I have configured MMC3 for SDIO communiction. but still sdio communication
is not up.
If clock is not enabled by default for MMC3 how can it be done in device
tree,
dmesg log shows:
[4.259093] omap_hsmmc 4781.mmc: unable to get vmmc regulator -517
Device tree configurations.
Hi,
When i add wl12xx module, none of the functions from wl12xx and wlcore are
getting called.
logs:
root@arm:~# modprobe wlcore_sdio
[ 48.682409]
[ 48.682409] ** wl1271_init
[ 48.690385]
[ 48.690385] ** sdio_register_driver
[ 48.708615]
[
Hi,
As a follow up I agree with the previous statement that wl127x drivers have
no device tree support. So you'll need to merge device tree support from
wl18xx drivers. As far as I can remember there are no major changes to
parameters passed by device tree to WiFi driver from wl127x to wl18xx. As
why not? this package enables wl12 for TI's am335x EVMSK and uses the
device tree
http://www.ti.com/tool/PROCESSOR-SDK-AM335X
2015-08-19 16:49 GMT+03:00 Dileep drdilee...@gmail.com:
Wl12xx will not support device tree. Need to find out other procedure to
enable in some board init function
Wl12xx will not support device tree. Need to find out other procedure to
enable in some board init function
On Wed, Aug 19, 2015 at 7:03 PM, Maxim Podbereznyy lisar...@gmail.com
wrote:
I don't see a wl12 boot message when the firmware is successfully loaded
2015-08-19 16:32 GMT+03:00 Maxim
I don't see a wl12 boot message when the firmware is successfully loaded
2015-08-19 16:32 GMT+03:00 Maxim Podbereznyy lisar...@gmail.com:
did you place t-connectivity directory to /lib/firmware?
2015-08-19 9:05 GMT+03:00 Dileep D R drdilee...@gmail.com:
Hi,
Interfacing wifi module
did you place t-connectivity directory to /lib/firmware?
2015-08-19 9:05 GMT+03:00 Dileep D R drdilee...@gmail.com:
Hi,
Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable
to bring up wlan0 interface, please guide me for proper device tree
configuration.
After
Hi,
Which wilink device are you building for?
The wl18xx family is now fully supported in 4.1 kernel. There is a device tree
file for the wl1835 cape in the kernel that is best place to look.
If you are looking at wl127x or wl128x then device tree will be similar but
you'll need to build the
Hi,
Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable
to bring up wlan0 interface, please guide me for proper device tree
configuration.
After booting excecuted
modprobe wlcore_sdio
modprobe wl12xx
Below are my configurations.
Kernel : 4.1
Rootfs : Debian
Device
14 matches
Mail list logo