The horror story of linux kernel

[crocket]

Let me explain the horror story. (The short version // Linux kernel let dependencies slip through cracks. It took days for a mere user like me to debug the issue.)

DRM_RADEON should depend on DRM_FBDEV_EMULATION and I2C_CHARDEV, but it doesn't.
Without DRM_FBDEV_EMULATION, DRM_RADEON loses video signal on all virtual consoles and garbles an X session for the first few seconds.
Without I2C_CHARDEV, DRM_RADEON becomes white on all virtual consoles.

DRM_RADEON should not initialize before I2C_CHARDEV. Because DRM_RADEON is oblivious of I2C_CHARDEV, DRM_RADEON may or may not initialize before I2C_CHARDEV.
If I2C_CHARDEV=y and DRM_RADEON=m, DRM_RADEON never initializes before I2C_CHARDEV does. If I2C_CHARDEV=y and DRM_RADEON=y, DRM_RADEON may or may not initialize before I2C_CHARDEV does.

It took days of trial and error to pinpoint the cause of DRM_RADEON's issue. At first, I just guessed relevant kernel config options, but it was too inefficient. Eventually, I started comparing differences between kernel configs that work and those that don't.
Based on differences, my trials became more accurate. Eventually, I narrowed the issue down to DRM_FBDEV_EMULATION and I2C_CHARDEV.

What a horror story. I assumed linux kernel wouldn't let dependencies slip through cracks.

[NeddySeagoon]

crocket,

[bammbamm808]

[freke]

[proteusx]

So, for now, what are the best settings for I2C_CHARDEV, DRM_FBDEV_EMULATION and DRM_RADEON?

[crocket]