Home > Articles > Operating Systems, Server

Security in Your Pocket: OpenBSD on ARM

David Chisnall talks with Dale Rahn, the OpenBSD ARM port maintainer, about how OpenBSD support for handheld systems has improved over recent years, and why users and OEMs should consider it.
Like this article? We recommend

When you think about OpenBSD, if you think about OpenBSD at all, you probably think of firewalls and routers. Maybe servers, and possibly desktops (but probably not). Recent versions have nice sound and 3D support, so desktop use isn't too unlikely, but one thing you probably don't think of is handheld systems.

The handheld operating system market is largely owned by Symbian, although its market share has been eroding over the last few years. Linux is starting to make inroads, and some people still use WinCE devices (developers for the platform tell me that naming it "wince" was more accurate than most Microsoft product names). Given that Symbian now has a POSIX layer and Linux has always aimed toward POSIX compliance, it's starting to look as if handhelds may end up running a lot of the same software as desktops.

The First Ports

The initial port of OpenBSD was funded by DARPA; Dale Rahn, who was employed by the DARPA grant to OpenBSD, and who had formerly worked for Motorola on ARM simulations, received the donation of a desktop ARM system. After this initial port, he returned to Motorola. At the time, a number of Motorola's customers were interested in a UNIX-like system for ARM chips, but didn't want to use GPL'd code in their products. Dale was hired to work on a BSD-licensed system for these customers.

One of the first handheld platforms to excite the Free Software community was the Sharp Zaurus series. These clamshell machines featured a 416 MHz Intel ARM CPU and 64MB of RAM. Most importantly, they shipped with Linux. At the time they were introduced, flash was still very expensive, so instead they came with a microdrive—a tiny mechanical disk.

Running Linux meant that there was already support from a toolchain capable of building a similar system. In addition, most of the hardware was well documented. In 2005, a few OpenBSD developers got hold of Zaurus systems and began a port of their operating system. The Zaurus used the same system-on-chip (SoC) module as the mobile phones Dale had been working to support at Motorola.

A few of the OpenBSD developers still use the Zaurus, but it's starting to look a bit dated. The screen is quite small, and the processor is a lot slower than a modern ARM system. I asked Dale if he had his eye on any more-recent devices:

We had started to look into the Nokia N800; however, there wasn't quite enough information available to get the port started properly at the time.

Work was started on the Openmoko FreeRunner and Gumstix (PXA270) at h2k8 last November, but those projects have stalled since I have had little free time lately. At this point, both of those hardware [lines] have been discontinued, so it is unclear how far those ports will proceed.

The situation isn't quite as bad as it seems, though. A lot of devices are starting to appear based around the Cortex-A8, with Texas Instruments' OMAP3 series being the most popular, and Motorola's i.MX5 is a newer entrant aimed at the netbook market. Dale continued:

Upcoming devices which look interesting include Beagle Board and Gumstix Overo. I have temporary access to a Beagle Board, but to support it properly [I] would need one or two for development and regression testing.

A number of companies have announced that they're planning to produce netbooks based around ARM cores, and companies such as Dell are now shipping hybrid systems that have both x86 and ARM CPUs. Dale mentioned his interest in the Latitude ON feature in these systems, which uses an OMAP3 core in Dell laptops for instant-on support. By keeping the home directories on a separate partition, it would be possible to have OpenBSD/ARM and OpenBSD/x86 installed on such a machine, using one when on battery and the other when on main power.

OpenBSD gained a lot of clean hardware abstraction from NetBSD, and has maintained this since it was forked. All code in the base system is expected to be tested on several architectures, including i386 and SPARC64, which provide almost diametrically opposed sets of constraints. I asked Dale how much time it took to get the initial Zaurus port working:

Most of the work was done in a couple of months. I did the bulk of the work, with dlg@ doing most of the USB host, miod@ most of the display driver work, [and] uwe@ did most of the apm/suspend/cpu-speed changes.

This was a port from the Cats platform, a desktop ARM system based around an evaluation board (and generally loathed by most developers), but it required new drivers to be written for a lot of the hardware. I asked Dale how much effort was needed to add support for a new SoC:

Depends on if the family of chips is supported or not. Typically a family of chips will have the same (or very similar) timers and interrupt controllers. So these must be rewritten for each family; however, for a new version of the family of chips, it is just a minor tweak or reused.

Most platforms can be up and running on uart, with the basic devices (uart, tick timer, interrupt controller) running in a few days to a few weeks. However, supporting additional pieces, USB (host and client), SD, CF, gpio keyboards, audio can take quite a bit longer. It definitely helps if hardware is available to other developers for them to work on their different areas of expertise. A bigger problem exists when the processor core isn't supported; e.g., Cortex-A8 removed one of the features in the mmu that was being used, so the physical map code needs work to function with the new changes, W^X support can be added at that time.

Unlike x86, which has always aimed to be backwardly compatible (even a new, 64-bit, x86 chip can still boot MS-DOS 1.0), each new ARM instruction set revision typically includes a new set of privileged-mode instructions, and therefore needs extra support, as do all of the other devices integrated into the SoC. Fortunately, a lot of devices outside of the SoC are not attached via standard interfaces such as compact flash or USB ports. Once OpenBSD has a working device driver for the bus, these can all run using existing drivers. If a USB webcam works on OpenBSD, for example, it will work on any OpenBSD platform with a USB driver.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020