I believe all you have to do is:
a) return 0 from can_use_raw_overlays_menu() on the LiveView photo branch if there's no CONFIG_RAW_LIVEVIEW.
b) add a meaningful message in menu_set_warning_raw (like raw is not working in LiveView on this camera).
This code will be used whenever there's something that requires raw support (assumming it calls menu_checkdep_raw from its MENU_UPDATE_FUNC).
The problems is more complicated than this and will require more significant refactoring to make the menu items logical in the situation that raw is not available in LV. Basically all the menu items are currently setup to assume that if raw is available at all, it is available in LV. We have the 1100D where this is not the case, and the menu items are extremely confusing even if I just add a warning here.
Here's what I mean:
The Histogram menu item will say:
• Histogram RAW RGB, Log, Dots
Even if I'm in LV where the histogram is not RAW, it is RAW during QR, so which histogram are we talking about? One of the histograms will be RAW and one won't. How do we convey this logically to the user? We can't say RAW histogram isn't working, it is working, sometimes...
I think this merits a complete rethink of the entire Overlay menu. Maybe there should be three separate overlay configurations: Movie, LV, and QR (maybe even a 4th MovieRaw). Currently the Overlay menu is very nonsensical for anyone who is not extremely familiar with how it works, in terms of what settings apply in what particular situations.
I also don't think there's any particular reason to even give the user the choice of what type (RAW vs. YUV) of overlay to use. The particular situation totally determines the type that should be used:
h264? - always use YUV overlays
raw_rec/mlv? - always use raw overlays
photo?
picture_quality_raw? - use raw if available, otherwise warn that YUV is being used instead
picture_qualtiy_jpeg? - always use YUV
thoughts?