All of lore.kernel.org
 help / color / mirror / Atom feed
From: vincent guffens <v.guffens@imperial.ac.uk>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: pci support
Date: Sat, 06 May 2006 14:36:06 +0100	[thread overview]
Message-ID: <445CA646.7010704@imperial.ac.uk> (raw)

Hi!

I was wondering if there was still an interest in pci support as
discussed previously. That is a general interface exported by a module
such as

struct grub_pci_support
{
  /* My name.  */
  const char *name;

  void (*init)(void);
  void (*fini)(void);

  void (*adjust) (grub_pci_device_t p);

  /* Base Address Register helper functions. There are up to 6 BARs
     PCI_BASE_ADDRESS_{[0-5]} in the configuration space of each device */
  unsigned long (*bar_start) (grub_pci_device_t, unsigned int bar);
  unsigned long (*bar_size) (grub_pci_device_t, unsigned int bar);

  int (*find_capability) (grub_pci_device_t, int cap);

  /* Call HOOK with each pci device.  */
  grub_err_t (*iterate) (int (*hook) (grub_pci_device_t));

  /* Fill the pci device structure (romaddr, ioaddr, membase, irq)*/
  grub_err_t (*init_pdev) (grub_pci_device_t);

  /* Low level io functions.  */
  struct grub_pci_io_support *io;
};

which allows multiple implementations such as one for instance from
etherboot which I have now.

It was written original with the idea of importing the etherboot drivers
so I don't know if it would still be usefull. The implementation that I
have uses direct pci access which maybe does not fit very well with the
idea of using pxe later on as it will require dealing with some bios
stuff anyway. It is basically usefull now for the lspci command which
could be made to print some nice text just like the Linux lspci command.

If so, I can prepare a separated patch for it and prepare the changelog.

Cheers,

--
    Vincent Guffens



             reply	other threads:[~2006-05-06 13:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06 13:36 vincent guffens [this message]
2006-05-06 14:08 ` pci support Vesa Jääskeläinen
2006-05-06 14:46 ` Marco Gerards
2006-05-06 15:12   ` vincent guffens
2006-05-06 16:12     ` Marco Gerards
2006-05-06 16:25       ` vincent guffens
2006-05-06 17:07         ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28 14:03 PCI support Marco Gerards
2008-01-28 17:25 ` Robert Millan
2008-01-28 18:32   ` Marco Gerards
2008-01-28 19:08     ` Robert Millan
2008-01-29  8:40       ` Marco Gerards
2008-01-30 17:57 ` Marco Gerards
2008-01-30 18:44   ` Robert Millan
2008-01-30 20:08     ` Marco Gerards
2008-01-30 22:01       ` Robert Millan
2008-01-30 22:17         ` Marco Gerards
2008-01-30 22:25           ` Robert Millan
2008-01-31  8:51             ` Marco Gerards
2008-01-31 11:05               ` Robert Millan
2008-02-02 15:39                 ` Marco Gerards
2008-01-30 19:40   ` Yoshinori K. Okuji
2008-01-30 20:07     ` Marco Gerards
2001-10-12 18:38 Kevin Fry
2001-10-12 19:09 ` Dan Taylor

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=445CA646.7010704@imperial.ac.uk \
    --to=v.guffens@imperial.ac.uk \
    --cc=grub-devel@gnu.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.