On 21/01/16 21:37, Konrad Rzeszutek Wilk wrote:
On Thu, Jan 21, 2016 at 12:33:43PM -0800, Luis R. Rodriguez wrote:
Sure, do we know if that ICC compatible? Do we care? There are a
series of ICC hacks put in place on ipxe's original solution which
I've folded in, it seems that works but if we car
+ * To solve this problem linker tables can be used on Linux, it enables you to
+ * always force compiling of select features that one wishes to avoid bit-rot
+ * while still enabling you to disable linking feature code into the final
+ * kernel image or building certain modules if the features ha
On 04/09/14 11:48, Maarten Lankhorst wrote:
If not, Ard please go ahead with option #2 above. Overkill yes, but I've
done the single __attribute__() hacks in other projects and someone
(usually me) always eventually forgets to tag some instance.
It appears we just got lucky on arm64, since we d
On 20/08/14 20:05, Mantas Mikulėnas wrote:
On Wed, Aug 20, 2014 at 8:05 PM, Matt Fleming wrote:
On Wed, 13 Aug, at 07:44:49PM, Matt Fleming wrote:
At this point, I think modifying the max address is the best way to
debug this further, and figure out what address causes the hang.
Mantas, did
On 16/07/14 15:34, Matt Fleming wrote:
On Tue, 15 Jul, at 08:44:34AM, H. Peter Anvin wrote:
Do we know what the Windows bootloader does? I thought it did use the
EFI File Protocol?
Good question. I'm not sure what the answer is, I'll try and find some
time to take a look.
I'm in the middle
On 15/07/14 16:10, Matt Fleming wrote:
Going forward, I suspect any attempts to use the EFI File Protocol are
going to result in this kind of breakage, and that the only thing that
can be relied upon is the Disk I/O Protocol.
But doing Disk I/O would necessitate adding the in-kernel FAT driver t
6 matches
Mail list logo
