All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hindley <mark@hindley.uklinux.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.{9,10}: VIA DRM undefined symbols
Date: Mon, 3 Jan 2005 03:51:05 +0000	[thread overview]
Message-ID: <20050103035105.GA7231@hindley.uklinux.net> (raw)

Hi,

I have just tried to use the kernel via module for my CLE266 and get a
whole load of undefined symbols:


Jan  3 03:08:11 mercury kernel: Uniform CD-ROM driver Revision: 3.20
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_alloc
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_free
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_irq_by_busid
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_control
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_driver_register_fns
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_sg_cleanup
Jan  3 03:12:48 mercury kernel: via: Unknown symbol DRM_FIND_MAP
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_wait_vblank
Jan  3 03:12:48 mercury kernel: via: Unknown symbol viadrv_irq_uninstall

Looking back, this seems to have appeared in 2.6.9 with the introduction
of the capabilities bitmask. The via driver appears not to have been
converted.

I am still trying to understand the new structure. What else does the
missing viadrv_driver_register_fns need to set apart from
dev->driver_features?

Thanks

Mark

             reply	other threads:[~2005-01-03  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03  3:51 Mark Hindley [this message]
2005-01-03  8:37 ` 2.6.{9,10}: VIA DRM undefined symbols Dave Airlie

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=20050103035105.GA7231@hindley.uklinux.net \
    --to=mark@hindley.uklinux.net \
    --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 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.