Transfer Summit, Oxford, 7-8 September – play with an alpha board! *UPDATED Aug 31*

If you’re in the UK and can make it to Oxford on September 7-8, you might like to come to the Transfer Summit at Keble College. We’ll have a stand there on the 7th (Wednesday) where you can come and demo a Raspberry Pi yourself.

Update, Aug 31: A speaking slot has opened up, so Eben will also be talking from 14.20 – 14.50 on Wed 7 about our relationship with open source.

Come and say hi – we’d love to see you.

We’ve more conferences in the pipeline, which I’ll announce as speaker lists are confirmed. Watch this space!

Update, Aug 31: Ross from the Transfer Summit says in the comments:

We have a few sponsored passes available for the conference. It includes accomodation, all sessions and all food (including the fabulous gala-dinner).

If you think you deserve a free pass mail me at rgardler .at. opendirective.com telling me why. If I’m convinced of the value you will bring to the conference and participants like Raspberry Pi we might be able to help you.

Ross is after a few lines from you explaining how you will contribute to open source, open hardware and open innovation moving forwards. I know a lot of you are very involved in the open source community – so get emailing!


Video: Eben at the Bletchley Park Educating Programmers Summit

Eben gave a presentation about Raspberry Pi at the Educating Programmers Summit run by Jason Gorman of Codemanship last week. Many thanks to Codemanship for the video, and for all their support – enjoy!


Demo – Raspberry Pi running Quake 3

Here’s something to liven up your weekend: a video of the Raspberry Pi running Quake 3. We’re still working on ironing a few kinks out (specifically, there seems to be a library issue which means our framerate, while good, isn’t quite as spectacular as we know it can be; we’re working on it as I post this) – but this is what test boards are for, and we’re making great progress getting the boards running smoothly.

I know some of our forum members are interested in building custom cases for your own Raspberry Pis, and have been asking about the heat that the board generates when it’s working hard. We feel you should be fine with the sort of thermoplastic cases that some of you are hoping to make using 3d printers: the chip doing all the work in this clip was still under body temperature after I’d filmed this demo four times, and feels surprisingly cool to the touch. This is also, of course, great news for power consumption. I hope that some of you can come to one of the conferences we’ll be participating in over the next few months (details will appear here on the blog and on the forums later when we’re confirmed) and have a look for yourselves.

Obviously, the Raspberry Pi isn’t intended as a gaming platform, but it’s very satisfying to let the Broadcom BCM2835 application processor off the leash (yes, I’m allowed to give you the part number now) and see what it can do in this sphere nonetheless. As Eben notes in the clip above, we’re hoping to show you a video of a bunch of us playing Q3 Deathmatch on some networked Raspberry Pis in a few weeks’ time – just because we can.

 


The alpha boards are here!

Our alpha boards arrived from the factory earlier today. Dom has been able to boot Linux, and access the SD card and network. We’ll have some demos filmed for you by the end of the week, but in the meantime, we thought you might like a closer look at the board itself. Here’s a video of Eben talking about the board and some of the hardware on it. The background howling is Mooncake, the Raspberry Pi Cat, and the horrible grinding sounds during the closeups are signals that I need a new video camera.

The console output from Debian booting and pinging the BBC website is under the fold, if you want a closer look at what’s under the hood. (You can scroll the console window left and right.)

I’ve also got a couple of pictures here from Gert, who got snapping as soon as the box was opened this afternoon. These are nice hi-res pictures, so click through if you want all the gory detail. Thanks to Dom and Gert for all their work on getting things up and running today.

Raspberry Pi alpha board, top view

Raspberry Pi alpha board, straight out of the box. Top view.

Raspberry Pi alpha board, bottom view

Raspberry Pi alpha board, bottom view.

Linux version 2.6.35.7 (grayg@dc4-arm-01) (gcc version 4.5.1 (Broadcom-2708) ) #13 Wed May 25 10:21:37 BST 2011
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: BCM2708
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 20320
Kernel command line: dma.dmachans=0xf0 bcm2708_fb.FBWIDTH=1920 bcm2708_fb.FBHEIGHT=1080 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 rootwait nfsroot=10.177.66.43:/home/dc4/debian_nfs/root/files ip=dhcp -init=/bin/bash
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 80MB = 80MB total
Memory: 75848k/75848k available, 6072k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xff800000 - 0xffe00000   (   6 MB)
    vmalloc : 0xc5800000 - 0xd8000000   ( 296 MB)
    lowmem  : 0xc0000000 - 0xc5000000   (  80 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0025000   ( 116 kB)
      .text : 0xc0025000 - 0xc045b000   (4312 kB)
      .data : 0xc047a000 - 0xc04a2660   ( 162 kB)
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:85
timer_set_mode: unhandled mode:1
timer_set_mode: unhandled mode:3
Console: colour dummy device 80x30
Calibrating delay loop... 499.71 BogoMIPS (lpj=2498560)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
khelper used greatest stack depth: 7040 bytes left
NET: Registered protocol family 16
khelper used greatest stack depth: 6960 bytes left
hw perfevents: enabled with v6 PMU driver, 3 counters available
mailbox: Broadcom VideoCore Mailbox driver
bcm2708_vcio: mailbox at f800b880
bcm_power: Broadcom power driver
Serial: AMBA PL011 UART driver
dev:f1: ttyAMA0 at MMIO 0x8201000 (irq = 83) is a AMBA/PL011
console [ttyAMA0] enabled
Serial: Broadcom virtual UART driver
bcm2708_vuart: registered virtual UART @c4c69000 through MBOX f800b8a0
khelper used greatest stack depth: 6728 bytes left
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Slow work thread pool: Starting up
Slow work thread pool: Ready
FS-Cache: Loaded
CacheFiles: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
bcm2708_dma: DMA manager at c5810000
: registered virtual buttonsbits @c4c7f000 via MBOX f800b8a0
input: bcm2708_vcbuttons as /devices/platform/bcm2708_vcbuttons/input/input0
: registered buttonsbits @c4c4b000 through MBOX f800b8a0
input: bcm2708_vctouch as /devices/platform/bcm2708_vctouch/input/input1
: registered ledbits @c4c48000 through MBOX f800b8a0
audit: initializing netlink socket (disabled)
type=2000 audit(1.040:1): initialized
squashfs: version 4.0 (2009/01/31) Phillip Lougher
FS-Cache: Netfs 'nfs' registered for caching
fuse init (API version 7.14)
msgmni has been set to 148
cryptomgr_test used greatest stack depth: 6596 bytes left
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
BCM2708FB: registering framebuffer (1920, 1080)
BCM2708FB: start = 0xc4400000
Console: switching to colour frame buffer device 240x67
kgdb: Registered I/O driver kgdboc.
brd: module loaded
loop: module loaded
nbd: registered device at major 43
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
dwc_otg: version 2.90b 6-MAY-2010 (platform bus)
Core Release: 2.80a
Setting default values for core params
Finished setting default values for core params
c5840008 -> 1
Using Buffer DMA mode
Periodic Transfer Interrupt Enhancement - disabled
Multiprocessor Interrupt Enhancement - disabled
Dedicated Tx FIFOs mode
dwc_otg bcm2708_usb: DWC OTG Controller
dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
dwc_otg bcm2708_usb: irq 75, io mem 0x00000000
Init: Port Power? op_state=1
Init: Power Port (0)
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller
usb usb1: Manufacturer: Linux 2.6.35.7 dwc_otg_hcd
usb usb1: SerialNumber: bcm2708_usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: Unknown controller version (2). You may experience problems.
mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA
mmc0: BCM2708 SDHC host at 0x08300000 DMA 4 IRQ 20
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
registered taskstats version 1
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SD08G 7.63 GiB
mmcblk0:
usb 1-1: new high speed USB device using dwc_otg and address 2
usb 1-1: New USB device found, idVendor=0424, idProduct=9512
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
usb 1-1.1: new high speed USB device using dwc_otg and address 3
usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1.3: new high speed USB device using dwc_otg and address 4
usb 1-1.3: New USB device found, idVendor=050d, idProduct=0307
usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=2
usb 1-1.3: Product: USB 2.0 Hub [MTT]
usb 1-1.3: SerialNumber: 001
hub 1-1.3:1.0: USB hub found
hub 1-1.3:1.0: 7 ports detected
usb 1-1.3.4: new high speed USB device using dwc_otg and address 5
usb 1-1.3.4: New USB device found, idVendor=13b1, idProduct=0018
usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.3.4: Product: USB 2.0 Network Adapter ver.2
usb 1-1.3.4: Manufacturer:
usb 1-1.3.4: SerialNumber: 000000
asix 1-1.3.4:1.0: eth0: register 'asix' at usb-bcm2708_usb-1.3.4, ASIX AX88772 USB 2.0 Ethernet, 00:1a:70:8f:af:da
usb 1-1.3.6: new low speed USB device using dwc_otg and address 6
eth0: link down
usb 1-1.3.6: New USB device found, idVendor=046d, idProduct=c05a
usb 1-1.3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.3.6: Product: USB Optical Mouse
usb 1-1.3.6: Manufacturer: Logitech
input: Logitech USB Optical Mouse as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.6/1-1.3.6:1.0/input/input2
generic-usb 0003:046D:C05A.0001: input: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-bcm2708_usb-1.3.6/input0
Sending DHCP requests .
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.177.65.50
IP-Config: Complete:
     device=eth0, addr=10.177.65.50, mask=255.255.254.0, gw=10.177.64.1,
     host=10.177.65.50, domain=cam.broadcom.com, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.177.66.43, rootpath=
àLooking up port of RPC 100003/2 on 10.177.66.43
Looking up port of RPC 100005/1 on 10.177.66.43
VFS: Mounted root (nfs filesystem) on device 0:12.
Freeing init memory: 116K
modprobe used greatest stack depth: 4368 bytes left
INIT: àversion 2.88 bootingà
àstty used greatest stack depth: 4176 bytes left
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Activating swap...done.
Cleaning up ifupdown....
Setting up networking....
Loading kernel modules...vcos: [725]: vchiq: initialised, 251.0
modprobe used greatest stack depth: 3984 bytes left
done.
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
done.
Mounting local filesystems...mount: special device /dev/mmcblk0p1 does not exist
failed.
Activating swapfile swap...done.
Cleaning up temporary files....
Starting portmap daemon....
Starting NFS common utilities: statd.
Cleaning up temporary files....
Setting kernel variables ...done.
Running scripts in rcS.d/ took 14 seconds.
INIT: àEntering runlevel: 2ø
àUsing makefile-style concurrent boot in runlevel 2.
Starting portmap daemon...Already running..
Starting NFS common utilities: statd.
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: cron.
Starting NTP server: ntpd.
Starting OpenBSD Secure Shell server: sshd.
Starting internet superserver: xinetd.
Running scripts in rc2.d/ took 6 seconds.
à
Debian GNU/Linux squeeze/sid default-dc4 ttyAMA0

default-dc4 login: dc4
Password:

Last login: Fri Aug  5 18:11:19 UTC 2011 from dc4-arm-01.cam.broadcom.com on pts/0

Linux default-dc4 2.6.35.7 #13 Wed May 25 10:21:37 BST 2011 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

dc4@default-dc4:~$ ping bbc.co.uk

PING bbc.co.uk (212.58.241.131) 56(84) bytes of data.

64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=1 ttl=248 time=10.0 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=2 ttl=248 time=0.000 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=3 ttl=248 time=0.000 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=4 ttl=248 time=0.000 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=5 ttl=248 time=0.000 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=6 ttl=248 time=0.000 ms
64 bytes from virtual-vip-231.thdo.bbc.co.uk (212.58.241.131): icmp_req=7 ttl=248 time=0.000 ms

^C

--- bbc.co.uk ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 6050ms

rtt min/avg/max/mdev = 0.000/1.428/10.000/3.499 ms

dc4@default-dc4:~$

Logo competition

Raspberry tart

We need a logo so we can stop having to take photographs of every raspberry we see to illustrate posts like this with.

Here at Raspberry Pi, hardware and software design is something we’re rather better at than graphic design. That’s where you come in.

We need you to design us a logo. This is more of a challenge than you might think – ideally, we’re after something that will be recognisable at 1cm square (to be used on the device itself), but that we can also use on merchandise, stationery and in publicity materials in a larger format. Flexibility is important in colour as well as size. The logo should look good in b/w as well as in colour. No words should be incorporated other than the words “Raspberry Pi”- you can use the π symbol in the design, but the word “Pi” needs to be spelled out for people who don’t read Greek orthography, or who want to google us.

We need to register the logo as a trademark, which means that your logo can’t resemble or be derived from any other logo or copyrighted image.

We need the logo from you in two formats: one entry in scalable vector graphic format (EPS) and one 1000px square JPG for use on our website. Please steer clear of halftones and gradients unless created inside a vector graphics program. Color in the EPS version must be CMYK, no spot colours. And the fewer colours you can use, the better! Please keep your file size under 5MB once compressed, and email to logocontest@raspberrypi.org including your email and postal addresses, name and age (we need your age to ensure you can enter into the legal contract that winning the competition will result in). The competition closes at midnight on September 30 2011, BST.

No obscenity, and especially nothing incorporating pedobear or goatse man, please! Or if you do, please make it extra-humorous – we won’t use it, but it might afford us a giggle. (If you do not know what either pedobear or goatse man are, I encourage you not to google them. Really.)

The prize winner will see their logo used (and will be able to claim bragging rights forever), and will receive a Model B device and an invitation for two to our launch party (date tbc).

Here comes the tedious legal bit (and I’m sorry for making it nearly as long as the Apple licence agreement). Have a flick through before you enter.

Definitions

“Entry” means a logo design created by the Entrant for this Contest.

“Entrant” means the individual that offers the Entry under the terms of this Contest.

Eligibility

  1. The Contest is open only to individuals. The Contest is not open to companies, educational institutions, organizations, etc. or to groups associated with such institutions.
  2. Entrants must be of sufficient legal age and standing to enter into a contract with the Raspberry Pi Foundation as required below.

How to Enter

  1. Initial entries must be submitted by email to logocontest@raspberrypi.org. The entries must be submitted as a scalable vector graphic in EPS format, and also as a JPG. See the Submission Guidelines below for further information.
  2. The email must include the name, age, postal address, phone number and email address of the Entrant.
  3. There is no limit on the number of entries that may be submitted by any one Entrant.
  4. Entries must conform to the Submission Guidelines set out below. Entries which fail to do so will be rejected.
  5. The deadline for Entries is midnight (one minute after 2359) on September 30th 2011, BST.
  6. There is no fee to enter the Contest.

Submission Guidelines

Because of the requirement to register the logo as a Trademark, Entrants should take care to ensure that their Entries are not in any way similar to existing logos or other copyrighted images. A logo that cannot be registered as a Trademark, no matter how well crafted, cannot win the Contest.

Due to the requirements for high quality printing and re-sizing Entries must submitted in scalable vector graphic format (EPS). We advise against the use of halftones and gradients unless created inside a vector graphics program. Color in this version must be CMYK, no spot colors.

A JPG 1000 pixels square of the logo is also requested so that entries can be posted to the Raspberry Pi web site without the need for conversion.

The limit on attachment sizes for our email is 5Mb. If your submission exceeds this size, even after compression, please send the images individually and note clearly in your emails that you are doing so.

To recap, entry will consist of 2 files: the basic logo in EPS and JPG format. We are able to handle most common file compression formats.

Prizes

Subject to the legal requirements outlined above, the winning design will be announced on the Raspberry Pi website in October 2011.

The winning designer will receive:

  1. A Raspberry Pi Model B
  2. An invitation to the Raspberry Pi launch party for two people
  3. The right to use the basic logo and identify him/herself as the logo designer.

Judging and Selection of Winner

  1. The winning design will be selected by judges appointed for the purpose and by the Raspberry Pi Foundation. Their decision will be final. No further correspondence shall be entered into.
  2. The Raspberry Pi Foundation reserves the right not to select a winner if, in its sole discretion, no suitable entries are received.
  3. The Raspberry Pi Foundation reserves the right to disqualify any Entrant or Entry at its sole discretion. No correspondence shall be entered into.
  4. The winner will be required to sign a contract assigning all ownership of the logo to the Raspberry Pi Foundation.
  5. Accepting the prize constitutes permission for the Raspberry Pi Foundation to make public and otherwise use the winner’s name and country of residence for publicity purposes. Further personal data may be requested but is not required.
  6. No timetable is set for the announcement of a winner due to the need to confirm that the winning entry can be registered as a Trademark

Intellectual Property

  1. All submitted work must be original and not based on any pre-existing design.
  2. All Entries will become the sole property of the Raspberry Pi Foundation and may be displayed publicly on the Raspberry Pi web site.
  3. The winning entry will be registered by the Raspberry Pi Foundation as a Trademark and the Entrant agrees to transfer all right and title to the Entry to the Raspberry Pi Foundation in accordance with the Official Rules of this Contest.

Acceptance

Participation constitutes the Entrant’s full and unconditional agreement to and acceptance of these Official Rules. By participating in the Contest, the Entrant is representing and warranting that he/she has read and understood, and agrees to be bound by, these rules. Including the guides and rules referred to herein, these Official Rules constitute the entire agreement between the Entrant and the Raspberry Pi Foundation in relation to the Contest. They govern the Entrant’s participation and supersede any prior or other agreements between the Entrant and the Raspberry Pi Foundation and relating to the Contest.

About THE RASPBERRY PI FOUNDATION

The Raspberry Pi Foundation is a non-profit charitable organisation registered with the Charity Commission. It is our intention that no individual or corporation will profit from the Raspberry Pi Foundation owning of the rights to the logo.

Our lawyers have asked us to include the following small print.


Representations and Warranties

By participating in the Contest, the Entrant warrants and represents in connection with the Entry submitted as part of his/her participation in the Contest: (a) he/she is the sole and exclusive owner of (and free of any adverse claim by any person, firm, or corporation) all intellectual property rights in and to the Entry; (b) the Entry is original and the use of the Entry as described in these Official Rules will not infringe the proprietary rights, including without limitation the intellectual property rights, of any third party; (c) the use of the Entry, as described in these Official Rules, will be in compliance with any third-party licenses pertaining to the Entry; (d) the Entry is not obscene or libelous, and does not violate any rights of any third party, including but not limited to rights of privacy or publicity; (e) the Entry does not contain any virus, spyware, malware, trap door, worm, or any other device, mechanism or code that is injurious or damaging to software or hardware used in conjunction with the Entry; (f) the Entry and its use as described in these Official Rules will not violate any federal, provincial, state or local laws or ordinances; (g) no employer or educational or other establishment has any rights in the Entry; (h) the Entry is consistent with these Official Rules; and (i) he/she has the right to grant the license to the Raspberry Pi Foundation as required in these Official Rules.

Severability

When any provision of these Official Rules is found to be invalid by a court of competent jurisdiction, the parties nevertheless agree that the Court should endeavor to give effect to the intentions of the parties as reflected in the provision, and that the other provisions of these Official Rules remain in full force and effect.

Indemnity; Disclaimer of warranties; Limitation of Liability

By participating in the Contest, the Entrant agrees to be bound by these Official Rules, including all eligibility requirements and all decisions of WSFS. By participating in the Contest, the Entrant agrees to indemnify, defend, and hold harmless the Raspberry Pi Foundation and its officers, agents, affiliates, contractors, contributors, subsidiaries, licensors and distributors (“Raspberry Pi Entities”) from any and all liability, claims, or actions of any kind, including, without limitation, property damage, personal injury, and/or death, arising out of his/her (i) breach of any representation, warranty or covenant contained in these Official Rules; or (ii) participation in the Contest; (iii) acceptance and/or use or misuse of any prize in connection with the Contest; or (iv) any third party claim relating to any rights in any design submitted.

BY PARTICIPATING IN THE CONTEST, THE ENTRANT AGREES THAT WSFS ENTITIES MAKE NO WARRANTY, REPRESENTATION, OR GUARANTEE OF ANY KIND, EXPRESSED OR IMPLIED, IN FACT OR IN LAW, RELATING TO THE CONTEST AND/OR THE PRIZES.

By participating in the Contest, the Entrant agrees that the Raspberry Pi Foundation is not responsible, and will in no event be held liable, for any: (a) lost, late, illegible, misdirected, damaged, incomplete, corrupted or garbled entries; (b) telephone, computer, or network malfunction or error; (c) communication disruption or other disruptions related to Internet traffic, virus, bug, worm, or non-authorized intervention; or (d) damage caused by a computer virus or otherwise resulting to any computer from the submission of entries. If such malfunction, error, disruption, or damage occurs or impairs the administration, security, fairness, or integrity of the Contest, the Raspberry Pi Foundation may, in its sole discretion, suspend, modify or terminate the Contest by posting a notice at http://www.raspberrypi.org. If the Contest is terminated before the scheduled end of the Contest Period, the Raspberry Pi Foundation will determine the winner from all eligible entries received as of the termination date. Persons found tampering with or abusing any aspect of the Contest, or whom the Raspberry Pi Foundation believes to be causing or attempting or intending to cause any malfunction, error, disruption, or damage will be disqualified. The Raspberry Pi Foundation reserves the right to disqualify any unauthorised entries.

NOTWITHSTANDING ANYTHING HEREIN TO THE CONTRARY, AND ONLY TO THE MAXIMUM EXTENT PERMISSIBLE BY THE APPLICABLE LAW, BY PARTICIPATING IN THE CONTEST, THE ENTRANT AGREES THAT IN NO EVENT WILL THE RASPBERRY PI FOUNDATION OR ANY RASPBERRY PI ENTITY BE LIABLE TO ENTRANTS OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES, REGARDLESS OF THE BASIS OR NATURE OF THE CLAIM, RELATING IN ANY MANNER TO THESE OFFICIAL RULES, THE CONTEST OR THE ENTRANT’S PARTICIPATION THEREIN, EVEN IF THE RASPBERRY PI FOUNDATION OR A RASPBERRY PI ENTITY WERE EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ALSO NOTWITHSTANDING ANYTHING HEREIN TO THE CONTRARY, BY PARTICIPATING IN THE CONTEST, THE ENTRANT FURTHER AGREES THAT IN NO EVENT WILL THE LIABILITY OF THE RASPBERRY PI FOUNDATION OR ANY RASPBERRY PI ENTITY RELATING IN ANY MANNER TO THESE OFFICIAL RULES, THE CONTEST OR THE ENTRANT’S PARTICIPATION THEREIN EXCEED THE GREATER OF UK£1,000 OR ANY OTHER AMOUNTS PAID BY THE ENTRANT TO ENTER INTO THE CONTEST. SOME JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CERTAIN INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO THE ENTRANT. IN THE EVENT THAT THE PRECEDING RELEASE IS DETERMINED BY A COURT OF COMPETENT JURISDICTION TO BE INVALID OR VOID FOR ANY REASON, THE ENTRANT AGREES THAT, BY ENTERING THE CONTEST, (I) ANY AND ALL DISPUTES, CLAIMS, AND CAUSES OR ACTION ARISING OUT OF OR IN CONNECTION WITH THE CONTEST, OR ANY PRIZES AWARDED, SHALL BE RESOLVED INDIVIDUALLY WITHOUT RESORT TO ANY FORM OF CLASS ACTION; AND (II) ANY CLAIMS, JUDGEMENTS AND AWARDS SHALL BE LIMITED TO ACTUAL OUT-OF-POCKET COSTS INCURRED, INCLUDING COSTS ASSOCIATED WITH ENTERING THE CONTEST, BUT IN NO EVENT ATTORNEY’S FEES.

For the avoidance of doubt, to the extent that English and Welsh law applies, nothing in these Official Rules shall limit or exclude either party’s liability for fraud, or for death or personal injury caused by its negligence, or any other liability to the extent such liability cannot be excluded or limited as a matter of law.

Interpretation; Governing Law; Jurisdiction

Interpretation. In the case of any dispute about the interpretation of the Rules, the Raspberry Pi Foundation’s decision as to the interpretation shall be final and Entrant shall be bound by the Raspberry Pi Foundation’s decision.

Governing Law. The interpretation and enforcement of these Official Rules will be governed by the laws of England and Wales, except to the extent required to be governed by the local law in the place of residence of an Entrant. The Contest is subject to all applicable, as the case may be, national, federal, provincial, state and local laws. The Entrant and the Raspberry Pi Foundation agree to the extent permitted by law to submit all disputes arising out of or relating to these Official Rules or the Contest to, and hereby waive any objection to the exclusive jurisdiction and venue of the courts of England and Wales. Subject to Section 5 above, if necessary any provision of these Official Rules which is found to be invalid by a court of competent jurisdiction shall be deemed to be struck out from these Official Rules.

Consideration

The Entrant agrees that the ability to participate in the Contest and to compete for the prizes offered in connection with the Contest constitute, where required, sufficient consideration for the Entrant’s obligations under these Official Rules.