All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Burke <tburke-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Platform development position at Red Hat
Date: Mon, 10 Jan 2005 11:22:59 -0500	[thread overview]
Message-ID: <41E2ABE3.1070309@redhat.com> (raw)

Hi All,

We have a position available at Red Hat which may be of interest to some 
people on this list.
Position: Kernel Platform Engineer
Company: Red Hat
Location: Westford, Massachusetts, USA

Responsible for low-level kernel platform support of x86 and x86-64 
systems. Relevant subsystems include ACPI, memory and interrupt 
controllers, IO and DMA controllers, and firmware/BIOS interfaces.  In 
this role you will be responsible for enhancing Red Hat's product set to 
be operational with new hardware from a wide range of vendors.  In Red 
Hat's unique position as a fully open source company, you will be 
working with, and contributing code to the upstream Linux community.

Requirements include 3 or more years of active Linux kernel 
development.  Demonstrated upstream involvement and contribution is a 
strong plus.  Prior experience in platform support is a prerequisite.  
Strong communication skills are required as you will be engaged with the 
upstream community as well as a range of hardware vendors.

If interested, please send your resume to Tim Burke, tburke-H+wXaHxf7aKXj1p+fO2waQ@public.gmane.org



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

                 reply	other threads:[~2005-01-10 16:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41E2ABE3.1070309@redhat.com \
    --to=tburke-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.