Specifications

SHARP CORPORATION
Sharp SL-series Zaurus “Qtopia” Development Start-up Guide
Ver 1.11, February 28, 2003, 7/63
Software Specifications Differences
The following table summarizes the overall software difference between the SL-5500 and the SL-5600. Please
also consult the following sections and additional documents on the developer website
(http://www.zaurus.com/dev/ ).
ITEMS SL-5500 SL-5600
Linux Kernel
Linux 2.4.6 (Embedix) Linux 2.4.18 (Embedix)
File System
Internal RAM: ext2 Internal Flash: JFFS2
*2)
Memory Area
Internal Storage:
approx. 31.8MB
Program Memory (work area):
approx. 28.1MB
Internal Flash Storage:
approx. 35MB
Program Memory (work area):
approx. 29.1KB
PIM database
XML based DTM
*3)
based
quickexec (*4)
Not supported Supported
Process Owner
Root user (as default
*4)
)
(root privilege possible)
USB
Network USB IO / Network
Screen Saver
Not supported Supported
S
O
F
T
W
A
R
E
Support style
(Theme)
- Windows
- Light
- QPE
- Windows
- Light
- QPE
- SLStyle
- ZIvory
- ZBlue
- Zpurple
(NOTE)
*2) JFFS2 file system is not a block device and thus swap cannot be created on the file system.
*3) DTM (DaTa Manager) is a set of modules that provide database functions to the applications. User applications can
utilize the SL data manager class to easily implement store, sort, and search data entities. Applications that utilize the
XML file format for the SL-5500 PIM information can also run on the SL-5600. However, all of the default PIM
applications on the SL-5600 now adopt and are managed by the DTM (PIM database). Thus, any 3
rd
party PIM
applications that access the XML files of the SL-5500 PIM applications will not run as expected. Developers need to
incorporate the DTM access for those PIM applications.
*4) Processes are executed with user privileges, and thus some directories may not be accessed depending on the
permissions granted. User applications must be executed with root privilege if the application will have access to the
directories at which only root privileges are granted. See section 3 and Appendix A for the details of the SL-5600
directories from “/”.