ARM's multiply-mapped memory mess
ARM's multiply-mapped memory mess
Posted Oct 16, 2010 22:33 UTC (Sat) by jzbiciak (guest, #5246)In reply to: ARM's multiply-mapped memory mess by marcH
Parent article: ARM's multiply-mapped memory mess
gets() is still in the C language, despite it being next to impossible to use safely. But if you link against it, some platforms give you a big scary warning. If you're standards-conforming, you have to have it though. Removing it is an API/ABI change.
In some ways, the situation with ARM's memory remapping sounds similar: a dangerous practice that seems to work suitably, despite the potential for it to go pear shaped when you least expect.
Posted Oct 17, 2010 13:04 UTC (Sun)
by marcH (subscriber, #57642)
[Link]
... whereas ioremap() is a Linux internal.
> despite it being next to impossible to use safely.
... whereas using ioremap() safely is not a problem.
> Removing it is an API/ABI change.
... whereas no one suggests removing ioremap().
> In some ways, the situation with ARM's memory remapping sounds similar
Not really.
ARM's multiply-mapped memory mess