On Jan 6, 2016, at 12:59 PM, Rick Thomas wrote:
> At a minimum, the patch in bug#781874 needs to be applied in order to be
> compatible with modern version of u-boot.
Oooops! Sorry! Brain-fart… The patch doesn’t do what I thought it did.
What I should have said is:
At a minimum, the file
On Jan 6, 2016, at 9:10 AM, Vagrant Cascadian wrote:
>> So I guess it’s all explained by https://bugs.debian.org/781874 .
>
> I really don't understand the logic outlined in that bug report, and
> your results don't exactly come to the same conclusion, which is why
> I've never "fixed" it.
Wel
On 2016-01-06, Rick Thomas wrote:
> For what it’s worth, by grepping about in /dev/mtd0, I located what
> seems to be the place where the u-boot environment is located.
>
> It’s 0x8.
>
> And to verify that, I have changed /etc/fw_env.config to
>
>> # MTD device name Device offset Env. size
This site's MAYBE worth looking at: http://www.plugcomputer.org/plugforum/
On 1/6/16, Vagrant Cascadian wrote:
> On 2016-01-06, Rick Thomas wrote:
>> I’ll try your 2016.01~rc3+dfsg1-3 from experimental as soon as I can.
>
> Great, thanks.
>
>
>> Just to be sure of what I need to do:
>>
>> 1) Inst
On 2016-01-06, Rick Thomas wrote:
> I’ll try your 2016.01~rc3+dfsg1-3 from experimental as soon as I can.
Great, thanks.
> Just to be sure of what I need to do:
>
> 1) Install the new versions of Debian packages for u-boot and u-boot-tools on
> my test SheevaPlug Debian (currently running Sid)
On Jan 5, 2016, at 10:12 PM, Vagrant Cascadian wrote:
>>> There are a couple bugs reported against u-boot which may be relevent:
>>>
>>> https://bugs.debian.org/781874
>>> https://bugs.debian.org/782293
For what it’s worth, by grepping about in /dev/mtd0, I located what seems to be
the place
On Jan 5, 2016, at 10:12 PM, Vagrant Cascadian wrote:
> On 2016-01-05, Rick Thomas wrote:
>> On Jan 5, 2016, at 12:17 PM, Vagrant Cascadian wrote:
>>> Well, I would like to know if the newer versions in Debian are or aren't
>>> working, if you'd be willing to try. They do still build in 2016.01
On 2016-01-05, Rick Thomas wrote:
> On Jan 5, 2016, at 12:17 PM, Vagrant Cascadian wrote:
>> Well, I would like to know if the newer versions in Debian are or aren't
>> working, if you'd be willing to try. They do still build in 2016.01~rc3,
>> so newer versions probably have converted over to gen
On Jan 5, 2016, at 12:17 PM, Vagrant Cascadian wrote:
> On 2016-01-05, Rick Thomas wrote:
>> On Jan 5, 2016, at 11:16 AM, Rick Thomas wrote:
>>> The only thing I see that looks like a warning is a mention of it not
>>> using “generic board”.
>>
>> It turns out that this may, in fact, be releva
On 2016-01-05, Rick Thomas wrote:
> On Jan 5, 2016, at 11:16 AM, Rick Thomas wrote:
>> The only thing I see that looks like a warning is a mention of it not
>> using “generic board”.
>
> It turns out that this may, in fact, be relevant. Googling for
> “README.generic-board” gives
>
> https://
10 matches
Mail list logo
