<!DOCTYPE html>
<html lang="en" data-content_root="../../../">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>The Intel Assabet (SA-1110 evaluation) board — The Linux Kernel documentation</title>
<link rel="stylesheet" type="text/css" href="../../../_static/pygments.css?v=fa44fd50" />
<link rel="stylesheet" type="text/css" href="../../../_static/alabaster.css?v=3918102e" />
<script src="../../../_static/documentation_options.js?v=5929fcd5"></script>
<script src="../../../_static/doctools.js?v=9bcbadda"></script>
<script src="../../../_static/sphinx_highlight.js?v=dc90522c"></script>
<link rel="index" title="Index" href="../../../genindex.html" />
<link rel="search" title="Search" href="../../../search.html" />
<link rel="next" title="CerfBoard/Cube" href="cerf.html" />
<link rel="prev" title="Intel StrongARM 1100" href="index.html" />
<link rel="stylesheet" href="../../../_static/custom.css" type="text/css" />
</head><body>
<div class="document">
<div class="sphinxsidebar" role="navigation" aria-label="Main">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="../../../index.html">
<img class="logo" src="../../../_static/logo.svg" alt="Logo of The Linux Kernel"/>
</a></p>
<h1 class="logo"><a href="../../../index.html">The Linux Kernel</a></h1>
<p class="blurb">6.18.50</p>
<search id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="../../../search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>
<p>
<h3 class="kernel-toc-contents">Contents</h3>
<input type="checkbox" class="kernel-toc-toggle" id = "kernel-toc-toggle" checked>
<label class="kernel-toc-title" for="kernel-toc-toggle"></label>
<div class="kerneltoc" id="kerneltoc">
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../process/development-process.html">Development process</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../process/submitting-patches.html">Submitting patches</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../process/code-of-conduct.html">Code of conduct</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../maintainer/index.html">Maintainer handbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../process/index.html">All development-process docs</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../core-api/index.html">Core API</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../driver-api/index.html">Driver APIs</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../subsystem-apis.html">Subsystems</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../locking/index.html">Locking</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../process/license-rules.html">Licensing rules</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../doc-guide/index.html">Writing documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../dev-tools/index.html">Development tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../dev-tools/testing-overview.html">Testing guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../kernel-hacking/index.html">Hacking guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../trace/index.html">Tracing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../fault-injection/index.html">Fault injection</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../livepatch/index.html">Livepatching</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../rust/index.html">Rust</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../admin-guide/index.html">Administration</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../kbuild/index.html">Build system</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../admin-guide/reporting-issues.html">Reporting issues</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../tools/index.html">Userspace tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../userspace-api/index.html">Userspace API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../firmware-guide/index.html">Firmware</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../devicetree/index.html">Firmware and Devicetree</a></li>
</ul>
<ul class="current">
<li class="toctree-l1 current"><a class="reference internal" href="../../index.html">CPU architectures</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="../../arc/index.html">ARC architecture</a></li>
<li class="toctree-l2 current"><a class="reference internal" href="../index.html">ARM Architecture</a><ul class="current">
<li class="toctree-l3"><a class="reference internal" href="../arm.html">ARM Linux 2.6 and upper</a></li>
<li class="toctree-l3"><a class="reference internal" href="../booting.html">Booting ARM Linux</a></li>
<li class="toctree-l3"><a class="reference internal" href="../cluster-pm-race-avoidance.html">Cluster-wide Power-up/power-down race avoidance algorithm</a></li>
<li class="toctree-l3"><a class="reference internal" href="../firmware.html">Interface for registering and calling firmware-specific operations for ARM</a></li>
<li class="toctree-l3"><a class="reference internal" href="../interrupts.html">Interrupts</a></li>
<li class="toctree-l3"><a class="reference internal" href="../kernel_mode_neon.html">Kernel mode NEON</a></li>
<li class="toctree-l3"><a class="reference internal" href="../kernel_user_helpers.html">Kernel-provided User Helpers</a></li>
<li class="toctree-l3"><a class="reference internal" href="../memory.html">Kernel Memory Layout on ARM Linux</a></li>
<li class="toctree-l3"><a class="reference internal" href="../mem_alignment.html">Memory alignment</a></li>
<li class="toctree-l3"><a class="reference internal" href="../tcm.html">ARM TCM (Tightly-Coupled Memory) handling in Linux</a></li>
<li class="toctree-l3"><a class="reference internal" href="../setup.html">Kernel initialisation parameters on ARM Linux</a></li>
<li class="toctree-l3"><a class="reference internal" href="../swp_emulation.html">Software emulation of deprecated SWP instruction (CONFIG_SWP_EMULATE)</a></li>
<li class="toctree-l3"><a class="reference internal" href="../uefi.html">The Unified Extensible Firmware Interface (UEFI)</a></li>
<li class="toctree-l3"><a class="reference internal" href="../vlocks.html">vlocks for Bare-Metal Mutual Exclusion</a></li>
<li class="toctree-l3"><a class="reference internal" href="../porting.html">Porting</a></li>
<li class="toctree-l3"><a class="reference internal" href="../features.html">Feature status on arm architecture</a></li>
<li class="toctree-l3 current"><a class="reference internal" href="../index.html#soc-specific-documents">SoC-specific documents</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../../arm64/index.html">ARM64 Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../loongarch/index.html">LoongArch Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../m68k/index.html">m68k Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../mips/index.html">MIPS-specific Documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../nios2/index.html">Nios II Specific Documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../openrisc/index.html">OpenRISC Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../parisc/index.html">PA-RISC Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../powerpc/index.html">powerpc</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../riscv/index.html">RISC-V architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../s390/index.html">s390 Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../sh/index.html">SuperH Interfaces Guide</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../sparc/index.html">Sparc Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../x86/index.html">x86-specific Documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../xtensa/index.html">Xtensa Architecture</a></li>
</ul>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../staging/index.html">Unsorted documentation</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../../translations/index.html">Translations</a></li>
</ul>
</div>
<script type="text/javascript"> <!--
var sbar = document.getElementsByClassName("sphinxsidebar")[0];
let currents = document.getElementsByClassName("current")
if (currents.length) {
sbar.scrollTop = currents[currents.length - 1].offsetTop;
}
--> </script>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../../../_sources/arch/arm/sa1100/assabet.rst.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
</div>
</div>
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<section id="the-intel-assabet-sa-1110-evaluation-board">
<h1>The Intel Assabet (SA-1110 evaluation) board<a class="headerlink" href="#the-intel-assabet-sa-1110-evaluation-board" title="Link to this heading">¶</a></h1>
<p>Please see:
<a class="reference external" href="http://developer.intel.com">http://developer.intel.com</a></p>
<p>Also some notes from John G Dorsey <<a class="reference external" href="mailto:jd5q%40andrew.cmu.edu">jd5q<span>@</span>andrew<span>.</span>cmu<span>.</span>edu</a>>:
<a class="reference external" href="http://www.cs.cmu.edu/~wearable/software/assabet.html">http://www.cs.cmu.edu/~wearable/software/assabet.html</a></p>
<section id="building-the-kernel">
<h2>Building the kernel<a class="headerlink" href="#building-the-kernel" title="Link to this heading">¶</a></h2>
<p>To build the kernel with current defaults:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>make assabet_defconfig
make oldconfig
make zImage
</pre></div>
</div>
<p>The resulting kernel image should be available in linux/arch/arm/boot/zImage.</p>
</section>
<section id="installing-a-bootloader">
<h2>Installing a bootloader<a class="headerlink" href="#installing-a-bootloader" title="Link to this heading">¶</a></h2>
<p>A couple of bootloaders able to boot Linux on Assabet are available:</p>
<p>BLOB (<a class="reference external" href="http://www.lartmaker.nl/lartware/blob/">http://www.lartmaker.nl/lartware/blob/</a>)</p>
<blockquote>
<div><p>BLOB is a bootloader used within the LART project. Some contributed
patches were merged into BLOB to add support for Assabet.</p>
</div></blockquote>
<p>Compaq’s Bootldr + John Dorsey’s patch for Assabet support
(<a class="reference external" href="http://www.handhelds.org/Compaq/bootldr.html">http://www.handhelds.org/Compaq/bootldr.html</a>)
(<a class="reference external" href="http://www.wearablegroup.org/software/bootldr/">http://www.wearablegroup.org/software/bootldr/</a>)</p>
<blockquote>
<div><p>Bootldr is the bootloader developed by Compaq for the iPAQ Pocket PC.
John Dorsey has produced add-on patches to add support for Assabet and
the JFFS filesystem.</p>
</div></blockquote>
<p>RedBoot (<a class="reference external" href="http://sources.redhat.com/redboot/">http://sources.redhat.com/redboot/</a>)</p>
<blockquote>
<div><p>RedBoot is a bootloader developed by Red Hat based on the eCos RTOS
hardware abstraction layer. It supports Assabet amongst many other
hardware platforms.</p>
</div></blockquote>
<p>RedBoot is currently the recommended choice since it’s the only one to have
networking support, and is the most actively maintained.</p>
<p>Brief examples on how to boot Linux with RedBoot are shown below. But first
you need to have RedBoot installed in your flash memory. A known to work
precompiled RedBoot binary is available from the following location:</p>
<ul class="simple">
<li><p><a class="reference external" href="ftp://ftp.netwinder.org/users/n/nico/">ftp://ftp.netwinder.org/users/n/nico/</a></p></li>
<li><p><a class="reference external" href="ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/">ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/</a></p></li>
<li><p><a class="reference external" href="ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/">ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/</a></p></li>
</ul>
<p>Look for redboot-assabet*.tgz. Some installation infos are provided in
redboot-assabet*.txt.</p>
</section>
<section id="initial-redboot-configuration">
<h2>Initial RedBoot configuration<a class="headerlink" href="#initial-redboot-configuration" title="Link to this heading">¶</a></h2>
<p>The commands used here are explained in The RedBoot User’s Guide available
on-line at <a class="reference external" href="http://sources.redhat.com/ecos/docs.html">http://sources.redhat.com/ecos/docs.html</a>.
Please refer to it for explanations.</p>
<p>If you have a CF network card (my Assabet kit contained a CF+ LP-E from
Socket Communications Inc.), you should strongly consider using it for TFTP
file transfers. You must insert it before RedBoot runs since it can’t detect
it dynamically.</p>
<p>To initialize the flash directory:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis init -f
</pre></div>
</div>
<p>To initialize the non-volatile settings, like whether you want to use BOOTP or
a static IP address, etc, use this command:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fconfig -i
</pre></div>
</div>
</section>
<section id="writing-a-kernel-image-into-flash">
<h2>Writing a kernel image into flash<a class="headerlink" href="#writing-a-kernel-image-into-flash" title="Link to this heading">¶</a></h2>
<p>First, the kernel image must be loaded into RAM. If you have the zImage file
available on a TFTP server:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load zImage -r -b 0x100000
</pre></div>
</div>
<p>If you rather want to use Y-Modem upload over the serial port:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load -m ymodem -r -b 0x100000
</pre></div>
</div>
<p>To write it to flash:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis create "Linux kernel" -b 0x100000 -l 0xc0000
</pre></div>
</div>
</section>
<section id="booting-the-kernel">
<h2>Booting the kernel<a class="headerlink" href="#booting-the-kernel" title="Link to this heading">¶</a></h2>
<p>The kernel still requires a filesystem to boot. A ramdisk image can be loaded
as follows:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load ramdisk_image.gz -r -b 0x800000
</pre></div>
</div>
<p>Again, Y-Modem upload can be used instead of TFTP by replacing the file name
by ‘-y ymodem’.</p>
<p>Now the kernel can be retrieved from flash like this:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis load "Linux kernel"
</pre></div>
</div>
<p>or loaded as described previously. To boot the kernel:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>exec -b 0x100000 -l 0xc0000
</pre></div>
</div>
<p>The ramdisk image could be stored into flash as well, but there are better
solutions for on-flash filesystems as mentioned below.</p>
</section>
<section id="using-jffs2">
<h2>Using JFFS2<a class="headerlink" href="#using-jffs2" title="Link to this heading">¶</a></h2>
<p>Using JFFS2 (the Second Journalling Flash File System) is probably the most
convenient way to store a writable filesystem into flash. JFFS2 is used in
conjunction with the MTD layer which is responsible for low-level flash
management. More information on the Linux MTD can be found on-line at:
<a class="reference external" href="http://www.linux-mtd.infradead.org/">http://www.linux-mtd.infradead.org/</a>. A JFFS howto with some infos about
creating JFFS/JFFS2 images is available from the same site.</p>
<p>For instance, a sample JFFS2 image can be retrieved from the same FTP sites
mentioned below for the precompiled RedBoot image.</p>
<p>To load this file:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load sample_img.jffs2 -r -b 0x100000
</pre></div>
</div>
<p>The result should look like:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>RedBoot> load sample_img.jffs2 -r -b 0x100000
Raw file loaded 0x00100000-0x00377424
</pre></div>
</div>
<p>Now we must know the size of the unallocated flash:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis free
</pre></div>
</div>
<p>Result:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>RedBoot> fis free
0x500E0000 .. 0x503C0000
</pre></div>
</div>
<p>The values above may be different depending on the size of the filesystem and
the type of flash. See their usage below as an example and take care of
substituting yours appropriately.</p>
<p>We must determine some values:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>size of unallocated flash: 0x503c0000 - 0x500e0000 = 0x2e0000
size of the filesystem image: 0x00377424 - 0x00100000 = 0x277424
</pre></div>
</div>
<p>We want to fit the filesystem image of course, but we also want to give it all
the remaining flash space as well. To write it:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis unlock -f 0x500E0000 -l 0x2e0000
fis erase -f 0x500E0000 -l 0x2e0000
fis write -b 0x100000 -l 0x277424 -f 0x500E0000
fis create "JFFS2" -n -f 0x500E0000 -l 0x2e0000
</pre></div>
</div>
<p>Now the filesystem is associated to a MTD “partition” once Linux has discovered
what they are in the boot process. From Redboot, the ‘fis list’ command
displays them:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0x50000000 0x50000000 0x00020000 0x00000000
RedBoot config 0x503C0000 0x503C0000 0x00020000 0x00000000
FIS directory 0x503E0000 0x503E0000 0x00020000 0x00000000
Linux kernel 0x50020000 0x00100000 0x000C0000 0x00000000
JFFS2 0x500E0000 0x500E0000 0x002E0000 0x00000000
</pre></div>
</div>
<p>However Linux should display something like:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>SA1100 flash: probing 32-bit flash bus
SA1100 flash: Found 2 x16 devices at 0x0 in 32-bit mode
Using RedBoot partition definition
Creating 5 MTD partitions on "SA1100 flash":
0x00000000-0x00020000 : "RedBoot"
0x00020000-0x000e0000 : "Linux kernel"
0x000e0000-0x003c0000 : "JFFS2"
0x003c0000-0x003e0000 : "RedBoot config"
0x003e0000-0x00400000 : "FIS directory"
</pre></div>
</div>
<p>What’s important here is the position of the partition we are interested in,
which is the third one. Within Linux, this correspond to /dev/mtdblock2.
Therefore to boot Linux with the kernel and its root filesystem in flash, we
need this RedBoot command:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>fis load "Linux kernel"
exec -b 0x100000 -l 0xc0000 -c "root=/dev/mtdblock2"
</pre></div>
</div>
<p>Of course other filesystems than JFFS might be used, like cramfs for example.
You might want to boot with a root filesystem over NFS, etc. It is also
possible, and sometimes more convenient, to flash a filesystem directly from
within Linux while booted from a ramdisk or NFS. The Linux MTD repository has
many tools to deal with flash memory as well, to erase it for example. JFFS2
can then be mounted directly on a freshly erased partition and files can be
copied over directly. Etc...</p>
</section>
<section id="redboot-scripting">
<h2>RedBoot scripting<a class="headerlink" href="#redboot-scripting" title="Link to this heading">¶</a></h2>
<p>All the commands above aren’t so useful if they have to be typed in every
time the Assabet is rebooted. Therefore it’s possible to automate the boot
process using RedBoot’s scripting capability.</p>
<p>For example, I use this to boot Linux with both the kernel and the ramdisk
images retrieved from a TFTP server on the network:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>RedBoot> fconfig
Run script at boot: false true
Boot script:
Enter script, terminate with empty line
>> load zImage -r -b 0x100000
>> load ramdisk_ks.gz -r -b 0x800000
>> exec -b 0x100000 -l 0xc0000
>>
Boot script timeout (1000ms resolution): 3
Use BOOTP for network configuration: true
GDB connection port: 9000
Network debug at boot time: false
Update RedBoot non-volatile configuration - are you sure (y/n)? y
</pre></div>
</div>
<p>Then, rebooting the Assabet is just a matter of waiting for the login prompt.</p>
<p>Nicolas Pitre
<a class="reference external" href="mailto:nico%40fluxnic.net">nico<span>@</span>fluxnic<span>.</span>net</a></p>
<p>June 12, 2001</p>
</section>
<section id="status-of-peripherals-in-rmk-tree-updated-14-10-2001">
<h2>Status of peripherals in -rmk tree (updated 14/10/2001)<a class="headerlink" href="#status-of-peripherals-in-rmk-tree-updated-14-10-2001" title="Link to this heading">¶</a></h2>
<dl>
<dt>Assabet:</dt><dd><dl>
<dt>Serial ports:</dt><dd><dl class="simple">
<dt>Radio: TX, RX, CTS, DSR, DCD, RI</dt><dd><ul class="simple">
<li><p>PM: Not tested.</p></li>
<li><p>COM: TX, RX, CTS, DSR, DCD, RTS, DTR, PM</p></li>
<li><p>PM: Not tested.</p></li>
<li><p>I2C: Implemented, not fully tested.</p></li>
<li><p>L3: Fully tested, pass.</p></li>
<li><p>PM: Not tested.</p></li>
</ul>
</dd>
</dl>
</dd>
<dt>Video:</dt><dd><ul class="simple">
<li><p>LCD: Fully tested. PM</p></li>
</ul>
<blockquote>
<div><p>(LCD doesn’t like being blanked with neponset connected)</p>
</div></blockquote>
<ul class="simple">
<li><p>Video out: Not fully</p></li>
</ul>
</dd>
<dt>Audio:</dt><dd><p>UDA1341:
- Playback: Fully tested, pass.
- Record: Implemented, not tested.
- PM: Not tested.</p>
<p>UCB1200:
- Audio play: Implemented, not heavily tested.
- Audio rec: Implemented, not heavily tested.
- Telco audio play: Implemented, not heavily tested.
- Telco audio rec: Implemented, not heavily tested.
- POTS control: No
- Touchscreen: Yes
- PM: Not tested.</p>
</dd>
<dt>Other:</dt><dd><ul class="simple">
<li><p>PCMCIA:</p></li>
<li><p>LPE: Fully tested, pass.</p></li>
<li><p>USB: No</p></li>
<li><p>IRDA:</p></li>
<li><p>SIR: Fully tested, pass.</p></li>
<li><p>FIR: Fully tested, pass.</p></li>
<li><p>PM: Not tested.</p></li>
</ul>
</dd>
</dl>
</dd>
<dt>Neponset:</dt><dd><dl class="simple">
<dt>Serial ports:</dt><dd><ul class="simple">
<li><p>COM1,2: TX, RX, CTS, DSR, DCD, RTS, DTR</p></li>
<li><p>PM: Not tested.</p></li>
<li><p>USB: Implemented, not heavily tested.</p></li>
<li><p>PCMCIA: Implemented, not heavily tested.</p></li>
<li><p>CF: Implemented, not heavily tested.</p></li>
<li><p>PM: Not tested.</p></li>
</ul>
</dd>
</dl>
</dd>
</dl>
<p>More stuff can be found in the -np (Nicolas Pitre’s) tree.</p>
</section>
</section>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©The kernel development community.
|
Powered by <a href="https://www.sphinx-doc.org/">Sphinx 8.1.3</a>
& <a href="https://alabaster.readthedocs.io">Alabaster 0.7.16</a>
|
<a href="../../../_sources/arch/arm/sa1100/assabet.rst.txt"
rel="nofollow">Page source</a>
</div>
</body>
</html>