mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Stam, Michel [FINT]" <M.Stam@fugro.nl>
To: barebox@lists.infradead.org
Subject: RE: Barebox x86 IDE support
Date: Mon, 24 Mar 2014 10:37:48 +0100	[thread overview]
Message-ID: <C89EFD3CD56F64468D3D206D683A8D2203154121@ldam-msx2.fugro-nl.local> (raw)

Hello maintainers,

I was wondering if one of you has had time to verify these patches and apply them to trunk?

Kind regards,

Michel Stam

--

From: Stam, Michel [FINT] 
Sent: Friday, March 14, 2014 17:31 PM
To: 'barebox@lists.infradead.org'
Subject: Barebox x86 IDE support

Dear list,

While working on barebox recently, I decided to port a couple of patches  I made to an old barebox tree a few years ago, to fix the IDE ports on the x86 platform.

I had to work on the resource allocation a bit, as the current GIT repository does not allow IORESOURCE_IO type to be passed to dev_request_region( ) and friends. I tried to keep the interface the same as much as possible by using macros etc.
Please find that attached in 0001-common-driver-Allow-for-I-O-mapped-I-O-in-resource-r.patch. 

Next, I added support to the platform IDE interface to use I/O-mapped I/O, and added the necessary allocation to the generic_pc board.

I did have to add a call to ata_port_detect( ) to ide_port_register to actually get the drives to be probed. Without it the interface seems to be stuck in some sort of limbo. This patch is in 0002-x86-Add-support-for-IDE-on-the-legacy-I-O-ports.patch.

Lastly, I added an extra serial port to the generic_pc board. Most (legacy) PCs have support for 2 serial ports, it seemed useful to me.

What does puzzle me is that the arch/x86/boot/Kconfig mentions X86_VESA and X86_VGA support, but the files (console_vga.c and console_vesa.c) do not nor have ever existed. Is this a remnant from U-boot v1?

Best regards,

Michel Stam

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-03-24  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  9:37 Stam, Michel [FINT] [this message]
2014-03-25  8:18 ` Sascha Hauer
2014-03-25 11:04   ` Michel Stam
  -- strict thread matches above, loose matches on Subject: below --
2014-03-14 17:01 Stam, Michel [FINT]

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=C89EFD3CD56F64468D3D206D683A8D2203154121@ldam-msx2.fugro-nl.local \
    --to=m.stam@fugro.nl \
    --cc=barebox@lists.infradead.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