Recent Posts
1
Other - Installation/Removal / Re: FiiO M3K Install (Native port)
« Last post by Njones on Today at 09:17:06 PM »I chose Replace and that worked. On another note, The car play mode turns on and starts playing when the ignition is turned on but doesn't turn off when the ignition is turned off.
2
Other - Installation/Removal / Re: FiiO M3K Install (Native port)
« Last post by Njones on Today at 06:33:16 PM »Do I skip files or replace files when asked? System info was same as on screen
3
Other - Installation/Removal / Re: FiiO M3K Install (Native port)
« Last post by amachronic on Today at 05:18:22 PM »Did you check the version in System > Rockbox Info, or the version on the recovery screen? The recovery screen shows the bootloader version, not the version of Rockbox on your SD card.
Otherwise, all I can think of is maybe the new .rockbox accidentally ended up inside a subfolder? You only need to unzip the new version, and copy the new .rockbox folder to the root of the SD card.
Otherwise, all I can think of is maybe the new .rockbox accidentally ended up inside a subfolder? You only need to unzip the new version, and copy the new .rockbox folder to the root of the SD card.
4
New Ports / Re: Fiio M3k
« Last post by vitt13 on Today at 03:03:38 PM »Is it possible to extract XVortex .rockbox folder from his images? He seems to made a bunch of changes to standard theme and bigger font is one of them.Xhibition theme, credits to XVortex. https://www.mediafire.com/file/txji2isj04wmcm3/xhibition.zip/file
Pay attention: I included config.cfg for example. Make sure you don't replace your own.
Add the string to config manually, if you use customized config
Code: [Select]
font: /.rockbox/fonts/20-Terminus-Bold.fnt
wps: /.rockbox/wps/xhibition.wps
sbs: /.rockbox/wps/xhibition.sbs
backdrop: /.rockbox/backdrops/xhibition2.bmp5
Starting Development and Compiling / Re: Beginning steps in kernel disassembly and analysis
« Last post by amachronic on Today at 05:23:45 AM »you're on the right track. Another tip, I think I might've have discovered platform_device_add using this string: "%s.%d.auto". It's the only user of that string. platform_device_register is a small wrapper which calls platform_device_add, but it is hard to identify on its own. The latter function doesn't have many other callers though.
The chain of references should look something like this--
The chain of references should look something like this--
Code: [Select]
[initcall array] -> board_base_init() -> platform_device_register() -> platform_device_add()
knowing the two "ends" you just need to chase down the references and find board_base_init in the middle. BTW, the platform device array is an array of structs like struct { void* pdevice; void* pdata; int size; }. pdevice is a struct whose first member points to a name string so you can see what device you are dealing with, and pdata is a blob containing the useful info. And convieniently, size tells you how big the pdata struct is.6
Other - Installation/Removal / Re: FiiO M3K Install (Native port)
« Last post by Njones on June 16, 2021, 10:59:20 PM »Tried to update to the latest developmental build. Downloaded the M3K build, unzipped it. put it on the Sd card. Rebooted unit still shows the previous version. What am I doing wrong? Idon't need the dual boot so I'm not doing anything with that.
7
Starting Development and Compiling / Re: Beginning steps in kernel disassembly and analysis
« Last post by dconrad on June 16, 2021, 10:15:27 PM »Some real progress now!
I'm working through your example here, and I've identified - with a fair amount of certainty - the following:
It took me a minute to figure out that you can not only bookmark stuff, but rename everything so the things you discover can propagate through the code.
It also took a bit of studying, but I think I see how items are added to the __initcall0_start[] arrays - through some magical define sorcery that took me like an hour to stare at, they use the labels "early", "core", "postcore", "arch", "subsys", "fs", "device", and "late" to correspond to levels 0-7, and then add functions by calling, for example, core_initcall(octeon_no_pci_init); to add octeon_no_pci_init() to the list of functions to run in level 1. Am I on track? Or off base? Or do I get a penalty for mixing my metaphors?
I still haven't identified board_base_init though...
To give you an idea of something you're looking for -- the goal is not to disassemble the entire kernel after all-- check out this file: arch/mips/xburst/soc-x1000/chip-x1000/halley2/common/board_base.c. There's a function in it called board_base_init(). That's a function you want to locate, because it's the only place you can find a reference to platform_devices_array. Most platform_data structs which driver probe() functions will reference, are pointed to by this array, and from the platform_data struct you can learn GPIOs, details of the LCD interface configuration, clock speeds, and other useful stuff. I2C devices will probably be registered by board_base_init too. But some stuff will be hardcoded willy-nilly in the drivers. (I guess for a kernel you never update, maintainability is not a problem...)
Since board_base_init is an initcall it can be located in a table. See init/main.c, look for the initcall_levels array. And then look at the initcall_level_names below it. You can easily find the names array because it references a unique string "postcore". Once you find that you can find do_initcall_level() and from that, find initcall_levels. The initcalls are set up in one big table and the first entry of initcall_levels will point at the first one. You can trawl through the init calls one by one until you locate board_base_init(). That may require identifying a few other functions first, but the payoff is worth it because some information simply can't be found any other way.
I'm working through your example here, and I've identified - with a fair amount of certainty - the following:
- start_kernel()
- pr_notice()
- parse_args()
- "postcore" string
- initcall_level_names[]
- do_initcall_level()
- initcall_levels[]
- initcallx_start[] (0 through 7)
It took me a minute to figure out that you can not only bookmark stuff, but rename everything so the things you discover can propagate through the code.
It also took a bit of studying, but I think I see how items are added to the __initcall0_start[] arrays - through some magical define sorcery that took me like an hour to stare at, they use the labels "early", "core", "postcore", "arch", "subsys", "fs", "device", and "late" to correspond to levels 0-7, and then add functions by calling, for example, core_initcall(octeon_no_pci_init); to add octeon_no_pci_init() to the list of functions to run in level 1. Am I on track? Or off base? Or do I get a penalty for mixing my metaphors?
I still haven't identified board_base_init though...
8
Theming and Appearance Customization / Re: [320x240] Tile based main menu
« Last post by Frankenpod on June 16, 2021, 06:15:56 PM »@millim
Sounds as if you have honed-in on the problem. Dealing with the Rockbox code itself is, as the phrase has it "above my pay-grade", so I'd rather leave it to any devs who care to take an interest to sort out. I wonder to what extent it's the same problem I've found with custom %vi statements that aren't tile-based? Difficult to provide a screenshot as they don't seem to happen the same way in the simulator as on the ipod. Either the text and background come out the same colour (regardless of what colours you tell it to use) for selected lines that are long enough to trigger scrolling, or, even more weirdly, the scrolling fails to work correctly and the text instead of scrolling just sort of smears itself like wet ink being smudged across a page.
Sounds as if you have honed-in on the problem. Dealing with the Rockbox code itself is, as the phrase has it "above my pay-grade", so I'd rather leave it to any devs who care to take an interest to sort out. I wonder to what extent it's the same problem I've found with custom %vi statements that aren't tile-based? Difficult to provide a screenshot as they don't seem to happen the same way in the simulator as on the ipod. Either the text and background come out the same colour (regardless of what colours you tell it to use) for selected lines that are long enough to trigger scrolling, or, even more weirdly, the scrolling fails to work correctly and the text instead of scrolling just sort of smears itself like wet ink being smudged across a page.
9
Theming and Appearance Customization / Re: [320x240] Tile based main menu
« Last post by millim on June 16, 2021, 04:50:09 PM ».. well had to investigate a bit how things play together 
. Yes, making it un-conditional works also for me. Do you plan to add this fix for the next release?
BTW, I have also added pictureflow to the main menu. It was already partially there, only three lines of code are necessary to make it work. Would also be nice if you can consider this extension.
I have attached the code with these modifications.
millim
. Yes, making it un-conditional works also for me. Do you plan to add this fix for the next release? BTW, I have also added pictureflow to the main menu. It was already partially there, only three lines of code are necessary to make it work. Would also be nice if you can consider this extension.
I have attached the code with these modifications.
millim
10
Rockbox General Discussion / Re: work on best low cost mp3 player for rockbox
« Last post by 7o9 on June 16, 2021, 04:05:10 PM »achakian0000 that is a screen protector, not the actual player.