Hey Jonas, On Friday 18 June 2010 12:05:07 Jonas Gorski wrote: > Hi Florian, > > On 17 June 2010 23:40, Florian Fainelli <flor...@openwrt.org> wrote: > > Most likely you will not be able to use a fixup just like the neufbox4 > > because that one still contains a valid identifier somewhere on the > > flash. > > Yeah, I figured that too. > > > I guess the only solution we have is to pass some informations to the > > kernel in the imagetag format. You might want to use one of the unused > > imagetag fields in struct bcm_tag such as information1 to pass > > informations to the kernel and set it to your model. It should not break > > other boards so this is an acceptable solution to me. > > Sounds good. information1 is still in the "reserved for future use" > range in the 4.02 SDK, so I assume it is safe to use. > > As far as I can see browsing through the code, I would do the following: > > 1. Extend imagetag with an additional parameter to set this field. > 2. Add a Build/Image/W500V* and call it in bcm63xx/image/Makefile > 3. Add a fixup to the kernel in setup.c that checks for it (also, add > the board info itself).
Indeed, these are the steps involved. As a start for the name, I would simply suggest Speedport W500V ;) > > *The name is debatable, perhaps there are other devices that might > need this too. > > > To be frank, I would like to avoid using the MIPS machine infrastructure > > as long as we can to keep the changes between upstream and openwrt > > minimal. > > While using the MIPS machine infrastructure is probably The Right > Thing(TM) to do, I don't see how this has anything to do with > identifying a board. I meant the command-line patching which is done by the image creation sorry. > > > Tell me if you need help implementing this. > > Thanks for the offer. Be prepared to be nagged on IRC if I get stuck ;-) -- Florian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
