Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:What's the point? (Score 1) 222

Yes but linux kernel need a direct ram mapping. And kernel mapping is 1G.
That's why highmem exist .

However, many people insist on using more than 1GB of physical memory on such a 32 bit system. This makes it necessary for the Linux kernel to jump through some interesting hoops... Basically the system uses the following tactics: * Memory above the physical address of 896MB are temporarily mapped into kernel virtual memory whenever the kernel needs to access that memory. * Data which the kernel frequently needs to access is allocated in the lower 896MB of memory (ZONE_NORMAL) and can be immediately accessed by the kernel (see Temporary mapping). * Data which the kernel only needs to access occasionally, including page cache, process memory and page tables, are preferentially allocated from ZONE_HIGHMEM. * The system can have additional physical memory zones to deal with devices that can only perform DMA to a limited amount of physical memory, ZONE_DMA and ZONE_DMA32. * Allocations and pageout pressure on the various memory zones need to be balanced (see Memory Balancing).

Cortex A15 uses 40-bit physical addressing is really useless : it is x86 PAE

Comment Re:What's the point? (Score 1) 222

But 64 bits is really interesting for the kernel. With Linux you can only map 1G of map without using segmentation (highmem).

Using 64 bits kernel with 32 bit programs solve the issue. And that's what is done on sparc, ppc, mips...

Also some algorithm really need 64 bits arithmetic to be faster.

Comment Re:Apple's security (Score 1) 315

It's mathematically impossible to make a device completely safe from someone who has complete physical control over it. You can encrypt this and that all you like, but it's literally only a matter of time before someone applies enough computing power and breaks said rights-management. Boot loaders can be heavily obfuscated against reverse engineering, but since the device has to actually boot and work at some point, there's a key to the proverbial lock in that haystack somewhere. I hope I'm making sense, coffee hasn't kicked in yet. You are wrong. First encryption is not used, it is digital signature (rsa). Second to be safe the first signature check should be done on the CPU ROM using internal RAM (no MITM). In this case if the signature algorithm is mathematically safe, you're device is broken if : - if somebody publish private key - if there bug in the ROM There can be others bugs/holes in upper layer of software (bootloader, kernel, ...), they can be patched by an update.

Comment Re:Wait, what does Con Kolivas have to do with thi (Score 1) 549

Especially since on a 64 bit distro pretty much everything, with very few exceptions is 64 bit.
You should look at ppc and sparc distro : pretty much everything is ... 32 bit. That because 32bit is more efficiant than 64 bits (less code/data size). But on x86 that's different because that's on the same arch at all (not the same register/feature, ...).

Slashdot Top Deals

Digital circuits are made from analog parts. -- Don Vonada