Sounds like a good idea to create a branch of these but shouldn't that be done for other boards as well.
So when you intend to remove boards to create version 4.2 you create a 4.1 branch of the existing state with those boards included. Then remove all boards that need to be dropped. When it's handled this way it's probably easier to drop boards that aren't used actively and thereby dropping unnecessary maintenance work. BR Wim -----Original Message----- From: coreboot [mailto:[email protected]] On Behalf Of Peter Stuge Sent: Tuesday, October 27, 2015 9:35 AM To: [email protected] Subject: Re: [coreboot] Proposal: Removing obsolete & EOL boards and chipsets for 4.2 release Alex G. wrote: > > I'd like to start a discussion about boards, chipsets, drivers, or > > other code that can be removed from the tree. > > All of AGESA fam10 and fam15. With Raptop Engineering upstreaming > native support, I don't think we want to haul around the AGESA > implementations, which have been troublesome in the past. > > Actually, branch off those boards, keep them alive in their little > branch, but remove them from master. Hm maybe. It's important that the boards which use AGESA are still available somehow, so that they could be ported to coreboot init if someone has interest in doing that. Maybe a branch is good enough. //Peter -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
