1 files changed, 1 insertions, 1 deletions

diff --git a/libopie2/opiecore/device/odevice_zaurus.cpp b/libopie2/opiecore/device/odevice_zaurus.cpp
index 1434e69..e8b813e 100644
--- a/libopie2/opiecore/device/odevice_zaurus.cpp
+++ b/libopie2/opiecore/device/odevice_zaurus.cpp
@@ -106,25 +106,25 @@ struct z_button z_buttons_c700 [] = {
 //       class up into individual classes. We need three classes
 //
 //       Zaurus-Collie (SA-model  w/ 320x240 lcd, for SL5500 and SL5000)
 //       Zaurus-Poodle (PXA-model w/ 320x240 lcd, for SL5600)
 //       Zaurus-Corgi  (PXA-model w/ 640x480 lcd, for C700, C750, C760, and C860)
 //
 //       Only question right now is: Do we really need to do it? Because as soon
 //       as the OpenZaurus kernel is ready, there will be a unified interface for all
 //       Zaurus models (concerning apm, backlight, buttons, etc.)
 //
 //       Comments? - mickeyl.
 
-void Zaurus::init()
+void Zaurus::init(const QString&)
 {
     d->m_vendorstr = "Sharp";
     d->m_vendor = Vendor_Sharp;
     m_embedix = true;  // Not openzaurus means: It has an embedix kernel !
 
     // QFile f ( "/proc/filesystems" );
     QString model;
 
     // It isn't a good idea to check the system configuration to
     // detect the distribution !
     // Otherwise it may happen that any other distribution is detected as openzaurus, just
     // because it uses a jffs2 filesystem..