Thanks for putting me right, will have to look into this properly. I was mainly looking at Anaconda and F20 for my HP DL140 G3 servers which there are problems with the video with. On 14 March 2014 01:05, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > On Thu, 2014-03-13 at 14:38 +0000, Aaron Gray wrote: >> Not sure yet but Anaconda has some specialised support for CPU's >> presumably the processor name at a minimum. > > I'm not sure if I'm missing something or you are, but Anaconda doesn't > really distinguish between CPUs, and it does support ARM. anaconda is a > supported deployment method for Calxeda ARM systems in Fedora 20: > https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation#Calxeda_EnergyCore_.28HighBank_and_Midway.29 > > anaconda does have a concept of *platforms*. The various platforms are > defined in blivet these days, in fact, in blivet/platform.py: > > class X86(Platform): > class EFI(Platform): > class MacEFI(EFI): > class Aarch64EFI(EFI): > class PPC(Platform): > class IPSeriesPPC(PPC): > class NewWorldPPC(PPC): > class PS3(PPC): > class S390(Platform): > class ARM(Platform): > class omapARM(ARM): > > and used in several places in blivet and anaconda (mainly partitioning > and bootloader installation). 'Aarch64EFI' is for aarch64 systems using > UEFI firmware, IIRC. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
