HI,
On 28-06-17 17:18, Stefan Assmann wrote:
On 2017-06-28 17:09, Hans de Goede wrote:
> Hi,
>
> On 28-06-17 16:48, Stefan Assmann wrote:
>> On 2017-06-16 18:13, Hans de Goede wrote:
>>> ---
>>> baseconfig/x86/x86_64/CONFIG_AK8975 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_AXP20X_ADC | 1 +
>>> baseconfig/x86/x86_64/CONFIG_AXP20X_POWER | 1 +
>>> baseconfig/x86/x86_64/CONFIG_AXP288_ADC | 1 +
>>> baseconfig/x86/x86_64/CONFIG_AXP288_CHARGER | 1 +
>>> baseconfig/x86/x86_64/CONFIG_AXP288_FUEL_GAUGE | 1 +
>>> baseconfig/x86/x86_64/CONFIG_BATTERY_MAX17042 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_CHARGER_BQ24190 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_AXP288 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_GPIO | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_INTEL_INT3496 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_MAX3355 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_RT8973A | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_SM5502 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_EXTCON_USB_GPIO | 1 +
>>> baseconfig/x86/x86_64/CONFIG_GPIO_AXP209 | 1 +
>>> baseconfig/x86/x86_64/CONFIG_I2C_DESIGNWARE_CORE | 1 +
>>> baseconfig/x86/x86_64/CONFIG_I2C_DESIGNWARE_PCI | 1 +
>>> .../x86/x86_64/CONFIG_I2C_DESIGNWARE_PLATFORM | 1 +
>>> baseconfig/x86/x86_64/CONFIG_INPUT_AXP20X_PEK | 1 +
>>> baseconfig/x86/x86_64/CONFIG_INV_MPU6050_I2C | 1 +
>>> baseconfig/x86/x86_64/CONFIG_INV_MPU6050_IIO | 1 +
>>> baseconfig/x86/x86_64/CONFIG_MFD_AXP20X | 1 +
>>> baseconfig/x86/x86_64/CONFIG_MFD_AXP20X_I2C | 1 +
>>> baseconfig/x86/x86_64/CONFIG_SILEAD_DMI | 1 +
>>> baseconfig/x86/x86_64/CONFIG_USB_XHCI_PLATFORM | 1 +
>>> baseconfig/x86/x86_64/CONFIG_XPOWER_PMIC_OPREGION | 1 +
>>> kernel-x86_64-debug.config | 39
++++++++++++++--------
>>> kernel-x86_64.config | 39
++++++++++++++--------
>>> kernel.spec | 5 +++
>>
>> Hi Hans,
>>
>> thanks for making this change. I've been hoping for this for quite a
>> while now. I see you've only enabled the AXP288 on x86_64 which means
>> all baytrail devices, which are 32bit are left out.
>> Could you apply those changes to i686 as well?
>
> Bay Trail devices are 64 bit devices with a 32 bit UEFI BIOS,
> Fedora does not support 32 bit UEFI booting (AFAIK), but work is
> under way for F27 to support booting 64 bits Fedora on a 32 bit
> UEFI BIOS using a 32 bit grub2-efi which loads a 64 bits kernel.
Any pointers on how to rebuild grub in the correct way?
I'm currently using the grub binaries from RHEL-7.4, which adds
support for this (yes RHEL got support for this first), but I
started with local build binaries following one of the many
tutorials on the net (don't remember which one, sorry).
> I'm already using this setup, what I do is I boot from an
> USB SSD with a 64 bit install on which I've copied a manually
> build 32 bit EFI capable grub, and then manually format the
> Bay Trail device and just copy the entire filesystem over
> manually. For F27 the plan is to have the 32 bit grub build
> included on the 64 bit media, as well as have anaconda automatically
> deal with all this.
Nice, thanks for letting me know. I'm currently running on 32bit.
So you're running a 32 bit Fedora? Interesting I did not know we
support 32 bit UEFI systems in Fedora.
Regards,
Hans