Incorrect dependency between CONFIG_DMA_BCM2708 and CONFIG_DMA_BCM2835
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
Research direction
Start in drivers/dma/Kconfig and drivers/dma/bcm2835-dma.c, then reproduce the reported configuration with CONFIG_DMADEVICES enabled, CONFIG_DMA_BCM2708=m, and CONFIG_DMA_BCM2835=y. Done means the kernel builds successfully for that configuration and the resulting bcm2708-dmaengine.ko and bcm2835-dma.ko modules can be loaded without the reported failure or kernel oops.
Written by the indexing model from the issue text.
Description
Describe the bug
The relationship expressed in drivers/dma/Kconfig where DMA_BCM2708 is marked as "depends on DMA_BCM2835" is incorrect. Notably if the BCM2835 support is built into the kernel, then the BCM2708 support cannot be a module.
To reproduce
Configure a kernel, with DMA Engine support (CONFIG_DMADEVICES) enabled. Set CONFIG_DMA_BCM2708=m and CONFIG_DMA_BCM2835=y.
Expected behaviour
The kernel build should succeed. Further ideally the resultant bcm2708-dmaengine.ko and bcm2835-dma.ko modules should be loadable without kernel oops and provide useful functionality.
Actual behaviour
Kernel build fails on drivers/dma/bcm2835-dma.c due to bcm_dmaman_remove() and bcm_dmaman_probe() being absent.
System
Irrelevant. Any system which can successfully build one or more of armel, armhf or aarch64 kernels should be acceptable.
Additional context
I'm building a kernel somewhat closer to how most Linux distributions tend to build them. Many things as modules instead of built-in. I'm targeting one particular PI, but I'm trying to figure out exactly which kernel options are required.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·