Op 5 jul. 2014, om 23:16 heeft bruce bushby het
volgende geschreven:
>
> Looking much better:
> # ls -l /dev/*spi*
> crw---1 root root 153, 0 Jan 10 13:51 /dev/spidev0.0
> #
>
>
> I added an spidev childnode to my spi1 node like so:
>
> spi1: spi@01c06000
On Sun, Jul 6, 2014 at 10:54 AM, Chen-Yu Tsai wrote:
> On Sun, Jul 6, 2014 at 10:50 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 07/06/2014 04:26 PM, jonsm...@gmail.com wrote:
>>> My build is finished and 3.16-rc2 appears to be working with loadable
>>> modules...
>>>
>>> Looking at my trees I must
On Sun, Jul 6, 2014 at 10:50 PM, Hans de Goede wrote:
> Hi,
>
> On 07/06/2014 04:26 PM, jonsm...@gmail.com wrote:
>> My build is finished and 3.16-rc2 appears to be working with loadable
>> modules...
>>
>> Looking at my trees I must have encountered this before and then
>> forgotten that I fixed
Hi,
On 07/06/2014 04:26 PM, jonsm...@gmail.com wrote:
> My build is finished and 3.16-rc2 appears to be working with loadable
> modules...
>
> Looking at my trees I must have encountered this before and then
> forgotten that I fixed it by copying the module into my shared rootfs
> and making it
My build is finished and 3.16-rc2 appears to be working with loadable modules...
Looking at my trees I must have encountered this before and then
forgotten that I fixed it by copying the module into my shared rootfs
and making it loadable.
So can you do a probe-defer and defer retrying the firmwa
I'm still building to verify this, but it looks like I had a copy of
the 3.15 module in my rootfs that I had forgotten about and it was not
built in. When build finishes I will make sure 3.16-r2 is set up the
same way.
Can't these modules be built in and just keep doing probe-defer while
waiting o
I truncated that, here is the rest. Note the big gap between 2.46 and
7.56 seconds. That is rootwait waiting for the rootfs to be ready.
Ethernet link speed detection is quite slow on Cubietruck, it takes
about 5 seconds.
[2.469611] ALSA device list:
[2.472576] #0: sunxi-codec
[6.41
On Sun, Jul 6, 2014 at 9:06 AM, Hans de Goede wrote:
> It seems you've the module build in, I'm amazed it can find the firmware
> in time then, seems like the race between getting the rootfs mounted, and
> trying to load the firmware ends up favorable in your case.
>
> In general having the brcmfm
Hi,
On 07/06/2014 03:02 PM, jonsm...@gmail.com wrote:
> On Sun, Jul 6, 2014 at 8:15 AM, Hans de Goede wrote:
>> Hi,
>>
>> On 07/04/2014 06:50 PM, jonsm...@gmail.com wrote:
>>> So is AP6210 support in mainline 3.16-rc1? I don't have a wireless
>>> device when I boot it but I do get some log messag
On Sun, Jul 6, 2014 at 8:15 AM, Hans de Goede wrote:
> Hi,
>
> On 07/04/2014 06:50 PM, jonsm...@gmail.com wrote:
>> So is AP6210 support in mainline 3.16-rc1? I don't have a wireless
>> device when I boot it but I do get some log messages at boot
>>
>> Can the AP6210 be probed? I don't see any
Hi,
On 07/04/2014 08:53 PM, Henrik Nordström wrote:
> fre 2014-07-04 klockan 17:14 +0800 skrev Wills Wang:
>> +gctrl = readl(&mmchost->reg->gctrl);
>> +gctrl &= ~SUNXI_MMC_GCTRL_ACCESS_BY_AHB;
> The above line seems redundant / unnecessary.
These lines are based on read-mo
Hi,
On 07/05/2014 02:24 PM, jonsm...@gmail.com wrote:
> On Sat, Jul 5, 2014 at 6:43 AM, Julian Calaby wrote:
>> Hi Jon,
>>
>> On Sat, Jul 5, 2014 at 2:50 AM, jonsm...@gmail.com
>> wrote:
>>> So is AP6210 support in mainline 3.16-rc1? I don't have a wireless
>>> device when I boot it but I do ge
Hi,
On 07/04/2014 06:50 PM, jonsm...@gmail.com wrote:
> So is AP6210 support in mainline 3.16-rc1? I don't have a wireless
> device when I boot it but I do get some log messages at boot
>
> Can the AP6210 be probed? I don't see anything in the Cubietruck DTS
> loading the driver.
>
> This is
Hi,
On Sun, Jul 6, 2014 at 6:31 AM, Code Kipper wrote:
> lioka on irc had it working with 3.14 and linux next back in May. have you
> checked your config for missing parts? These are what I use for my A2000 to
> get wifi working on linux-next
> +# CHANGES FOR WIFI
> +CONFIG_MODULES=y
> +CONFIG_WI
14 matches
Mail list logo