The new version of this driver has a new build structure, is splitted into driver- and frontend-package and therefore requires a new ebuild. I created one, will attach this, that's working, but not very clean. Perhaps the build of frontand and/or frontend libs should be configurable via USE-flag. I compiled gigaset-isdn with my new ebuild but the kernel module does not work (the old version did not even compile with my kernel version). dmesg says: bas_gigaset: Unknown symbol gigaset_start bas_gigaset: Unknown symbol gigaset_dbg_buffer bas_gigaset: Unknown symbol gigaset_invtab bas_gigaset: Unknown symbol gigaset_add_event bas_gigaset: Unknown symbol gigaset_getunassignedcs bas_gigaset: Unknown symbol gigaset_freecs bas_gigaset: Unknown symbol gigaset_skb_sent bas_gigaset: Unknown symbol gigaset_handle_modem_response bas_gigaset: Unknown symbol gigaset_unassign bas_gigaset: Unknown symbol gigaset_if_receive bas_gigaset: Unknown symbol gigaset_initcs bas_gigaset: Unknown symbol gigaset_blockdriver bas_gigaset: Unknown symbol gigaset_initdriver bas_gigaset: Unknown symbol gigaset_freedriver bas_gigaset: Unknown symbol gigaset_stop bas_gigaset: Unknown symbol gigaset_shutdown when I try to insert the module.
Created attachment 74620 [details] gigaset-isdn-0.5.0.ebuild This ebuild compiles gigaset-isdn but the module cannot be inserted into kernel (linux-2.6.14)
Created attachment 74621 [details] gigaset-isdn-0.5.0.ebuild Got it, there's a new module named "gigaset". I added it to the MODULES_LIST, seems to work now!
version bumped. thanks for the tip!
