CONFIG_CAN disabled in kernel
Bug #327243 reported by
yope
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Karmic |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
Binary package hint: linux-image
lsb_release -rd:
Description: Ubuntu 8.10
Release: 8.10
package: linux-image-
CONFIG_CAN is not defined in the kernel configuration, making it hard to user the Socket-CAN protocol introduced in kernel 2.6.25.
It should be trivial to enable the following options:
CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_VCAN=y
That way one could actually use CAN interfaces (like Peak CAN) on ubuntu linux with the new socket-CAN API. One of the main reasons I upgraded in the first place ;-)
Changed in linux (Ubuntu Karmic): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This is not a bug in the linux-meta package, moving to the linux package.