On 26 February 2012 22:53, Mike Giacomelli giac2...@hotmail.com wrote:
I think the underlying problem is that people expect USB to work and we
don't make it clear to them that it does not work yet on all targets. I
think the best solution to this problem would be to display a warning
whenever
Am 27.02.2012 11:30, schrieb Torne Wuff:
I absolutely agree; while *our* definition of unstable includes is
missing USB support, the consistent surprise users demonstrate when
they find out is evidence enough that that definition is not obvious
:)
That's not quite right. We allow targets
On Sat, Feb 25, 2012 at 07:30:07PM -0700, Mike Giacomelli wrote:
I think the problem is that we did a release of rbutil that finally
started installing the new bootloader but that defaults to installing
the old release.
Rockbox Utility installs the *current* release.
Frank
--
Debugging is
On Sat, Feb 25, 2012 at 07:30:07PM -0700, Mike Giacomelli wrote:
I guess it'll get fixed when 3.11 comes out.
Will it? Is USB stable enough to be enabled in a stable release? I
haven't seen any discussion about that yet.
I sincerely hope that the answer won't be It will be enabled because
On 26/02/12 11:12, Frank Gevaerts wrote:
On Sat, Feb 25, 2012 at 07:30:07PM -0700, Mike Giacomelli wrote:
I guess it'll get fixed when 3.11 comes out.
Will it? Is USB stable enough to be enabled in a stable release? I
haven't seen any discussion about that yet.
I sincerely hope that the
On Sun, Feb 26, 2012 at 11:21:07AM +, Alex Parker wrote:
If USB is not to be enabled on 3.11, then we revert the bootloader
change. Rockbox Utility should be installing bootloaders that work
with the current release. If people are using current builds then
they can also install an
On 26/02/12 11:29, Frank Gevaerts wrote:
On Sun, Feb 26, 2012 at 11:21:07AM +, Alex Parker wrote:
If USB is not to be enabled on 3.11, then we revert the bootloader
change. Rockbox Utility should be installing bootloaders that work
with the current release. If people are using current
Am 26.02.2012 01:03, schrieb Frank Gevaerts:
Since USB was enabled on trunk to evaluate how well USB works, without
knowing if it will even be enabled in the next release, I must say I
fail to understand why mkamsboot got changed.
I agree (in hindsight, I too haven't thought of this issue when
On Sun, Feb 26, 2012 at 12:29 PM, Frank Gevaerts fr...@gevaerts.be wrote:
The way I understand it (which could be wrong) is that the dualboot code
(i.e. the bit that decides which bit gets to boot) is *not* in the
bootloader as in the files that are downloaded, but in bits of code
that's
On Sun, Feb 26, 2012 at 12:29 PM, Frank Gevaerts fr...@gevaerts.be wrote:
The way I understand it (which could be wrong) is that the dualboot code
(i.e. the bit that decides which bit gets to boot) is *not* in the
bootloader as in the files that are downloaded, but in bits of code
Hi,
It appears the new rockbox utility installs bootloaders on AMSv2 that
boot rockbox by default when USB is detected.
This basically means that for people installing 3.10, USB is broken
when they plug in the device while it's switched off. This is the way
*many* users use USB, which explains
Since USB was enabled on trunk to evaluate how well USB works, without
knowing if it will even be enabled in the next release, I must say I
fail to understand why mkamsboot got changed.
I think the problem is that we did a release of rbutil that finally started
installing the new
12 matches
Mail list logo
