Re: linux-next not booting on snowball

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 13, 2011 at 1:35 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
> On Wed, Dec 7, 2011 at 5:09 AM, Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> wrote:
>
>>> The kernel hangs at:
>>>
>>> u8500_map_io
>>>  -> ux500_map_io
>>>    -> ux500_read_asicid(addr=9001dbf4), base=9001d000
>>>      ->  readl(__io_address(9001dbf4)=f901dbf4);
>
> This code isn't strictly necessary so I moved it out of the way.
>
> Then it hangs on the second iotable_init() call instead.

I found the cause: overlapping iotable entries, sent a separate
patch, check it out...

The above remaps and reads from some random ROM page to get
the ASIC ID is actually not screwing things up. Right now.

Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux