Hello Mark, thank you for your advice. I figured out what I did wrong now. And my function has "bt" in its name and not "dt". So, don't worry, I don't mess with the DT there.
Greetings Sebastian Priebe ========================================== CADCON Ingenieurgesellschaft mbH & Co. KG Geschaeftsfuehrer: Robert Bauer, Andreas Gundel Sitz der Gesellschaft: D-86368 Gersthofen Registergericht: Amtsgericht Augsburg HRA 14521 ========================================== -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Mark Rutland Gesendet: Freitag, 1. August 2014 16:12 An: Priebe, Sebastian Cc: [email protected] Betreff: Re: core command line parameters with dt On Fri, Aug 01, 2014 at 02:55:42PM +0100, Priebe, Sebastian wrote: > Hello, > > I want to use kernel command line parameters within my machine file. > If I use the __setup macro I get the following build error: > error: __setup_str_model_bt causes a section type conflict with > myboard_dt_board_compat > > static const char *myboard_dt_board_compat[] __initconst = { > "vendor,model", > NULL > }; You have a section mismatch because your code evidently doesn't live in an init section, but is trying to access data which does. The fact that the data happens to be a list of compatible strings is irrelevant, and this is in no way related to dt. Figure out whether your function should live in an init section or if the data should not. Make sure that you don't reference anything in init section from anything else which does not itself live in an init section. That will solve your build issue. The name of the function sounds suspicious to begin with from a DT perspective. You shouldn't need to override DT properties from the command line. Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
