Hi Troy, > I'd like to help a little bit with the installation documentation, at least > with the boards I have and can verify the instructions. > > Do I just log in and edit the wiki page? > Or would it be better to send it here, or to pwhalen (who looks like he does > the edits)? Just edit the wiki straight up, it's easy enough to do further updates as necessary. Keeps it quick and simple and the wiki handles versioning etc. > Just incase it's to send things here. In the manual steps there are a few > things that would be good to change/add. > > BeagleBone: > The uboot directory has changed, so it is no longer beaglebone, but > am335x_boneblack. Please change > /usr/share/uboot/beaglebone/ > to > /usr/share/uboot/am335x_boneblack/ Just update it, it's already the case in fedora-arm-installer. > PcDuino: > The PcDuino family have the Allwinner A20 chipset, and fall in the same > instructions as Banana Pi and CubieBoard. But their names, and their uboot > names, are so horribly long. But it would be nice to have them in there > somehow. Could we possibly put them in the TARGET= line? > Something like > > TARGET= # Bananapi , CubieBoard , Cubieboard2 , Cubietruck > # Linksprite_pcDuino , Linksprite_pcDuino3 , > Linksprite_pcDuino3_Nano For fedora-arm-installer the upstream git repo is at [1], we need to improve the way we handle all the possible combinations of boards we possibly support to make it less manual and easier to support more boards without having to manually update them all. Ideas and suggestions welcome, patches even more so. Some sort of menu system based on SoC might be useful but I've not really had the time to look at it closely. Cheers, Peter [1] https://git.fedorahosted.org/git/fedora-arm-installer.git _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
