bhtooefr
Posts: 12
Joined: Tue Nov 15, 2011 11:28 am

How are duplicate, conflicting config.txt entries handled?

Mon Nov 12, 2012 11:37 pm

Is there a defined rule for how duplicate, conflicting config.txt entries are handled by the firmware? First item found? Last item found? Fail boot? And does that rule change depending on what the entry is?

I'm planning on developing a front-end to manipulate config.txt settings (for RISC OS), and want to know how to handle these edge cases.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5398
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: How are duplicate, conflicting config.txt entries handle

Tue Nov 13, 2012 12:36 am

We parse the list (once) in order, and store each value in a static array.

So, last entry wins.

bhtooefr
Posts: 12
Joined: Tue Nov 15, 2011 11:28 am

Re: How are duplicate, conflicting config.txt entries handle

Sun Nov 18, 2012 7:38 pm

What about cases such as, for instance, a user having hdmi_safe enabled, and then having some entries that conflict? I assume that it parses hdmi_safe as actually being all of the settings that it represents, and then those settings presented afterwards win?

Or, for instance, someone setting gpu_freq, then core_freq differently.

Return to “Advanced users”