Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 3 days, 18 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 4 days, 18 hrs ago - more...
|
2011-11-17
, 11:43
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#192
|
Originally Posted by pali
it will try to boot system from device /dev/mmcblk0p2 (mmc0, partition 2).
root command specify rootfs file system
| The Following User Says Thank You to pali For This Useful Post: | ||
|
|
2011-11-17
, 11:43
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#193
|
It means "Mount /dev/mmcblk0p2 as root filesystem and boot from it"
| The Following User Says Thank You to Fabry For This Useful Post: | ||
|
|
2011-11-17
, 11:48
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#194
|
Originally Posted by pali
Or try less RX51 patches.
it is problem with u-boot itself, not rx51 code. Somebody must find working version and then find commit which brings power consumption problem. can sombody do it? (al least find last working build of u-boot for rx51?)
For example a lastest version without patch for eMMC support has the high consumption problem ?
If not it is the hw registry manipulation (to activate eMMC) which generates the problem
|
|
2011-11-17
, 11:50
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#195
|
Got it thanks! Just as I thought. What made me confused about that command is it is used for Kubuntu mobile. The whole image is put on sd card which is an external card and should be /dev/mmcblk1p2 so I wondered why is it pointing on /dev/mmcblk0p2 yet it boots perfectly.
|
|
2011-11-17
, 17:27
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#196
|
Originally Posted by pali
Pali I'm not that accurately sure but it was your first u-boot version that worked for HW 2204 that is stable I think. next update I did was already on kp49 with new uboot and power consumption issue arised. Never documented it since I thought it was some devel apps I installed. But after reflashed never tried reinstalling it again until now
it is problem with u-boot itself, not rx51 code. Somebody must find working version and then find commit which brings power consumption problem. can sombody do it? (al least find last working build of u-boot for rx51?)
|
|
2011-11-19
, 02:55
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#197
|
Hi Pali! A friend of mine did lookup on the power consumption issue from her n900, tested every commit from git and said that uboot power consumption was ok before this commit.
https://gitorious.org/u-boot-shr/u-b...21b2046d4e000f
https://gitorious.org/u-boot-shr/u-b...21b2046d4e000f
|
|
2011-11-19
, 12:11
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#198
|
Originally Posted by Radicalz38
Are you sure if it is this commit?
Hi Pali! A friend of mine did lookup on the power consumption issue from her n900, tested every commit from git and said that uboot power consumption was ok before this commit.
https://gitorious.org/u-boot-shr/u-b...21b2046d4e000f
Code:
include/twl4030.h: Add power bus message definitions * Code from linux kernel: include/linux/i2c/twl.h
|
|
2011-11-19
, 15:31
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#199
|
A supposition :
This header adds value definitions (#define) used by other u-boot sources.
If the #define are missing the source code does nothing (or uses default values) but if the #define are present then they are used during Hw config and some of these #define generate misconfigured Hw
This header adds value definitions (#define) used by other u-boot sources.
If the #define are missing the source code does nothing (or uses default values) but if the #define are present then they are used during Hw config and some of these #define generate misconfigured Hw
|
|
2011-11-19
, 15:36
|
|
Posts: 2,153 |
Thanked: 8,462 times |
Joined on May 2010
|
#200
|
Originally Posted by Fabry
I know twl4030 part of u-boot source code. And this new definitions are not used in u-boot. I added it because in next commits I need use twl4030 regulator for enable eMMC...
A supposition :
This header adds value definitions (#define) used by other u-boot sources.
If the #define are missing the source code does nothing (or uses default values) but if the #define are present then they are used during Hw config and some of these #define generate misconfigured Hw
I got a feeling that it would map /dev/mmcblk0p2 as as root partition for the booted OS but I'm not sure that's why I asked.
Last edited by Radicalz38; 2011-11-17 at 11:42.