build options for via nano (eg. samsung nc20)

Bug #365631 reported by kieran on 2009-04-23
4
Affects Status Importance Assigned to Milestone
linux-ports (Ubuntu)
Undecided
Unassigned
Nominated for Jaunty by Barry Carroll

Bug Description

e_powersaver and padlock modules are not included. add the following to the .config to enable them.

CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_X86_E_POWERSAVER=m

Related branches

Andy Whitcroft (apw) wrote :

This is a request for new config options so this should be against the real kernel packages not -meta. Reassigning to the appropriate package.

affects: linux-ports-meta (Ubuntu) → linux-ports (Ubuntu)
Luke Yelavich (themuso) wrote :

Seems like the crypto options are set in the 386 kernel, but the main padlock code is in the kernel instead of a module. The AES and SHA options are built as modules.

However, the E_POWERSAVER option is not built, so I'll look at getting that enabled.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-ports - 2.6.30-2.3

---------------
linux-ports (2.6.30-2.3) karmic; urgency=low

  [ Luke Yelavich ]

  * [Config] Enable Keyspan USB serial device firmware in kernel module as
    per karmic mainline
  * [Config] Enable EFI partition support on powerpc and sparc
  * SAUCE: include asm/types.h in arch/ia64/include/asm/fpu.h
    - LP: #375509
  * [Config] disable CONFIG_AMIGAONE in powerpc kernel config
    - LP: #373131
  * [Config] Enable VIA C7 Enhanced PowerSaver support
    - LP: #365631

  Rebase on top of karmic mainline 2.6.30-5.6:

  [ Tim Gardner ]

  * [Config] Enable Keyspan USB serial device firmware in kernel module
    - LP: #334285

  [ Upstream Kernel Changes ]

  * rebased to 2.6.30-rc5

  [ Colin Watson ]

  * Build-Conflict with findutils (= 4.4.1-1ubuntu1), to avoid
    /usr/include/asm/* going missing
    - LP: #373214

 -- Luke Yelavich <email address hidden> Thu, 14 May 2009 21:59:52 +1000

Changed in linux-ports (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers