-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --> alternatively: ship coreboot without anything in src/mainboard. have git repositories for each vendor/mainboard. user downloads what they need, and a default .config for the board of their choosing.
On 25/03/14 23:29, The Gluglug wrote: > This is focussed on users (non-developers). > > Most coreboot users only have perhaps a few machines that they are > building for. Maybe even just one. > > Yet they are downloading the entire coreboot source tree and > selecting which board they want, configuring it, etc. > > My idea: --> a small set of source files (such as from > src/mainboard/vendor/board) --> a script (perhaps a simple git > checkout) which fetches the needed parts of the source from the > main branch, for building that board --> default/"sane" > configurations pre-defined for that board. > > Advantages: --> less headache for developers (user already has most > of what they need, less likely to request support) --> less to > download (less waiting required, especially for people with slow > connections) > > Essentially, I have in mind a more "modular" coreboot. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTMhIzAAoJEP9Ft0z50c+UHuYH/12yONytbAEMfmJ2erNUYLSG yimowCAGTAMndkrTC6NP5yOjUEZhUIFZD4zB6PvjVyIAo8OMilphrTpwTU/ZJB0r gqGPS7mieLbt6SfX3rA5n9B9Nqf5ijvHob2p9/1XPiVqyb1mmur0W+LEXd3ESWv3 Jtpo7jSqYg73NB4QBlHDNqYBH1bxIaqGNOSXjvgpnQgORTkC2yob7eTi8GV9gYBE UvdLFz0BfOgmzrtGpXLiDy0UFbU1BVeOTMrBJLiiZvjzNmhZAlp7XCFrWz8uH+yC hF+j3LCgrejGHPmakONia00hjctSocUZzec+ALVMqs96B2CEUiRbgGP0AwUyMk0= =938K -----END PGP SIGNATURE----- -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
