search for: 34727

...cards (with one small problem that involves moving a function somewhere -- seems like nouveau_crtc_set_config is defined in dispnv04 but used outside of it -- which I haven't done yet) the module size goes down to 721366, split up as: text data bss dec hex filename 346212 34727 480 381419 5d1eb ./drivers/gpu/drm/nouveau/nouveau.ko So another 130K of text, 26K of data, and 130K in symbols (?). I didn't have to do anything too dirty, with the mild exception of the device/base.c file which had that giant if statement, which will have to be done a bit more cleverl...

So... I was wondering what the impact of splitting up the card compilation by e.g. generation would be. Depending on the split things would get fairly intertwined, so I thought I'd start small. This just splits NVC0 from everything else. I figure that for the people this matters the most to, NVC0 is the least relevant card -- people with sub-1GB of RAM, older hardware. With my config options

...e 198669 9525 80 208274 32d92 drivers/gpu/drm/nouveau/nouveau.ko NV04: 710270 bytes text data bss dec hex filename 333755 35094 160 369009 5a171 drivers/gpu/drm/nouveau/nouveau.ko NV50: 722079 bytes text data bss dec hex filename 346476 34727 480 381683 5d2f3 drivers/gpu/drm/nouveau/nouveau.ko NVC0: 878726 bytes text data bss dec hex filename 360593 140327 80 501000 7a508 drivers/gpu/drm/nouveau/nouveau.ko NV04 + NV50: 995817 bytes text data bss dec hex filename 472244 59528...

...e5) RECORD: seq=35, uid=35, flags=0x00 - ext 0 keywords : (0000) - ext 1 mbox : 33755 (db83000000000000) - ext 2 header-md5: (2999d63f140b82744ff806650f3f92b4) RECORD: seq=36, uid=36, flags=0x00 - ext 0 keywords : (0000) - ext 1 mbox : 34727 (a787000000000000) - ext 2 header-md5: (b4cb756ed5b8ac6bc964d711f18bffdf) RECORD: seq=37, uid=37, flags=0x00 - ext 0 keywords : (0000) - ext 1 mbox : 35699 (738b000000000000) - ext 2 header-md5: (5a25c7f1025446412771693e06c745c7) RECORD: seq=38, ui...