From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: The Linux Kernel and Castle Technology Ltd, UK
Date: Mon, 10 Feb 2003 19:38:35 +0000 [thread overview]
Message-ID: <20030210193835.D15661@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030207151926.A30927@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Fri, Feb 07, 2003 at 03:19:26PM +0000
Castle Technology Limited ask me to post this press release to the
Linux Kernel mailing list.
By posting this press release, I wish to make it absolutely clear
that I am not expressing any views either way with respect to this
press release, merely passing the information on as requested.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-----------------------------[ cut here ]----------------------------
PRESS RELEASE
10th February 2003
Castle Technology Limited note with interest the recent discussion
regarding their IYONIX computer, the world's first desktop computer
to use the Intel XScale processor.
Following discussions with Russell King and with this in mind, Castle
should like to respond to claims originally proposed in Justin Fletcher's
"ReadMe.txt" file and Russell King's subsequent posting to the Linux
Kernel Mailing List.
The RISC OS 5.00 kernel did not contain work taken from or derived from
the ARM-Linux or Linux kernel.
The RISC OS 5.01 kernel did not contain work taken from or derived from
the ARM-Linux or Linux kernel.
The RISC OS 5.02 kernel does not contain work taken from or derived from
the ARM-Linux or Linux kernel.
There are no plans to use GPL derived code in any part of the RISC OS
kernel in the future.
For the avoidance of doubt, the hardware abstraction layer (roughly
analogous to a PC's BIOS) has it's PCI allocation and bridge setup
based in part on the following functions from the Linux kernel sources:
pci_alloc_primary_bus
pbus_size_bridges
pbus_assign_resources_sorted
pci_setup_bridge
pci_bridge_check_ranges
pbus_size_mem
pbus_assign_resources
pci_assign_unassigned_resources
pci_scan_bus
pcibios_update_resource
pci_read_bases
pci_alloc_bus
pci_add_new_bus
pci_do_scan_bus
pci_scan_bridge
pci_setup_device
pci_scan_device
pci_scan_slot
pcibios_fixup_bus
pci_calc_resource_flags
pci_size
pdev_fixup_device_resources
pbus_assign_bus_resources
pci_do_scan_bus
pcibios_fixup_pbus_ranges
pci_assign_resource
pdev_sort_resources
pdev_enable_device
pbus_size_io
Any company or individual wishing to receive a copy of the source code
to this component should apply in writing to:
The Managing Director
Castle Technology Ltd
Ore Trading Estate
Woodbridge Road
Framlingham
Suffolk
IP13 9LL
enclosing a formatted 3.5" floppy diskette and return postage stamps,
or international reply coupons for those outside the United Kingdom.
These sources will also form an integral part of a forthcoming Linux
port to the IYONIX.
With the tough goal of fitting all of the supporting software and
applications for the IYONIX computer into just 4Mbytes of ROM, later
issues of the supporting software have had to have function names
removed (along with a strategy of tokenising textual messages and
compressing binaries) to make room for, in particular, the support
for the 'boot keyboard' USB drivers.
Issued by Mike Williams on behalf of Castle Technology Ltd
next prev parent reply other threads:[~2003-02-10 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 15:19 The Linux Kernel and Castle Technology Ltd, UK Russell King
2003-02-07 15:41 ` Mailing Lists
2003-02-10 19:38 ` Russell King [this message]
[not found] <20030207153007$386b@gated-at.bofh.it>
2003-02-07 23:59 ` Alan J. Wylie
2003-02-08 1:19 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030210193835.D15661@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).