On Mon, Feb 21, 2011 at 3:01 PM, Erik Gilling <konkers@xxxxxxxxxxx> wrote: > On Mon, Feb 21, 2011 at 12:40 PM, Olof Johansson <olof@xxxxxxxxx> wrote: >> On Mon, Feb 21, 2011 at 11:31 AM, Erik Gilling <konkers@xxxxxxxxxxx> wrote: >>> Does the kernel still print an unknown atag message without this handler? >>> Is worth keeping an empty handler around to keep that from printing? >> >> With what firmware? u-boot doesn't pass many handlers at all. >> Shouldn't fastboot be changed to not pass it, if it's not used? >> >> (In other words, maybe it makes sense to keep it in android-tegra, but >> not upstream)? > > My experience was with nvidia's bootloader that came on the harmony > boards. Have they switched to u-boot? Their current public LDK contains their bootloader and a 2.6.32 kernel (and they're still using machine ID 3333 in that one). They have started upstreaming their u-boot port, but I don't what the plans are on what the LDK will use in the future. Will the nvidia atags ever be used in the kernel? If not, it'd make more sense to have the warning there so that the bootloader is fixed than having the no-op stub. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
