- l4-hackers - example.com Site

L4Linux and ACPI
by Marcel Selhorst 14 Oct '05

14 Oct '05

Hi, is it possible to compile L4Linux with ACPI-support? I get a mass of L4-errors. Attached you'll find the .config-file and the log. Thanks in advance, Marcel Selhorst # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-l4 # Fri Oct 14 09:09:06 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/Daten/CVS/fiasco/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y CONFIG_L4_L4ENV_MEMSIZE=32 # CONFIG_L4_TAMED is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # # Stub drivers # CONFIG_L4_BLK_DRV=y CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set # CONFIG_L4_SERIAL is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debuggin options # # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_EFI is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y # CONFIG_ACPI_SLEEP_PROC_SLEEP is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # # CONFIG_ISAPNP is not set # CONFIG_PNPBIOS is not set CONFIG_PNPACPI=y # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_SCSI is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set # CONFIG_EL16 is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y # CONFIG_DE2104X is not set CONFIG_TULIP=y # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y # CONFIG_8139CP is not set CONFIG_8139TOO=y CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SKGE is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=y # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # CONFIG_TCG_TPM=m # CONFIG_TCG_NSC is not set # CONFIG_TCG_ATMEL is not set CONFIG_TCG_INFINEON=m # # I2C support # # CONFIG_I2C is not set # CONFIG_I2C_SENSOR is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=y # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y # CONFIG_NFS_DIRECTIO is not set # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set CONFIG_CRYPTO_AES_586=y # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/l4/kernel/arch-i386/built-in.o(.init.text+0x896): In function `l4x_hybrid_return': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/kernel/arch-i386/dispatch.c:493: undefined reference to `acpi_reserve_bootmem' arch/l4/kernel/arch-i386/built-in.o(.init.text+0x8c1): In function `l4x_hybrid_return': /Daten/CVS/fiasco/l4linux-2.6/include/asm/l4x/syscall.h:12: undefined reference to `acpi_reserve_bootmem' arch/l4/kernel/arch-i386/built-in.o(.init.text+0xda5): In function `l4x_suspend_user': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/kernel/arch-i386/dispatch.c:981: undefined reference to `acpi_boot_table_init' drivers/built-in.o(.text+0x15f7a): In function `acpi_os_install_interrupt_handler': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/osl.c:291: undefined reference to `acpi_gsi_to_irq' drivers/built-in.o(.text+0x2c68d): In function `acpi_sleep_prepare': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/poweroff.c:27: undefined reference to `acpi_wakeup_address' drivers/built-in.o(.text+0x2c9a9): In function `acpi_pm_enter': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:81: undefined reference to `acpi_save_state_mem' drivers/built-in.o(.text+0x2c9dd):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:95: undefined reference to `do_suspend_lowlevel' drivers/built-in.o(.text+0x2c9f8):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:102: undefined reference to `do_suspend_lowlevel_s4bios' drivers/built-in.o(.text+0x2ca1f):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:120: undefined reference to `acpi_restore_state_mem' drivers/built-in.o(.text+0x2ca72): In function `acpi_pm_finish': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:145: undefined reference to `init_8259A' drivers/built-in.o(.text+0x305cc): In function `acpi_pci_irq_enable': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/pci_irq.c:470: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x305e9):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/pci_irq.c:479: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x3658a): In function `pnpacpi_allocated_resource': /Daten/CVS/fiasco/l4linux-2.6/drivers/pnp/pnpacpi/rsparser.c:170: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x36629):/Daten/CVS/fiasco/l4linux-2.6/drivers/pnp/pnpacpi/rsparser.c:159: undefined reference to `acpi_register_gsi' drivers/built-in.o(.init.text+0x2981): In function `pci_setup': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/pci.c:793: undefined reference to `acpi_irq_model' drivers/built-in.o(.init.text+0x29d9):/Daten/CVS/fiasco/l4linux-2.6/drivers/pci/pci.c:791: undefined reference to `acpi_irq_model' drivers/built-in.o(.init.text+0x2a96): In function `acpi_early_init': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/bus.c: undefined reference to `acpi_ioapic' drivers/built-in.o(.init.text+0x2ac5): In function `quirk_isa_dma_hangs': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/quirks.c:56: undefined reference to `acpi_pic_sci_set_trigger' drivers/built-in.o(.init.text+0x2ace): In function `quirk_nopcipci': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/quirks.c:77: undefined reference to `acpi_sci_override_gsi' arch/l4/pci/built-in.o(.text+0x943): In function `get_base_addr': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/../../i386/pci/mmconfig.c:26: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.text+0x951):/Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/../../i386/pci/mmconfig.c:26: undefined reference to `pci_mmcfg_config_nu arch/l4/pci/built-in.o(.init.text+0x41f): In function `pci_mmcfg_init': /Daten/CVS/fiasco/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h: undefined reference to `acpi_parse_mcfg' arch/l4/pci/built-in.o(.init.text+0x431): In function `pci_bios_read': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/pcbios.c:181: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.init.text+0x43a):/Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/pcbios.c:181: undefined reference to `pci_mmcfg_config'

2 3

Building device drivers with oskit10_support_l4env
by Jianjun Shen 13 Oct '05

13 Oct '05

Hi, I do not know why, but I posted this mail the day before yesterday, and has not found it in l4-hackers mail list (and got no reply). So I re-send the same mail. Sorry, if you receive it twice. I am trying to implement an ide server, and I think I can make use of oskit10_support. As a test, I wrote a simple program which calls start_blk_devices() to initialize block drivers. This test program works well when being linked with oskit10_support, but fails when being linked with oskit10_l4env_support_full. In the latter case, it takes quite a long time to probe irqs for each ide device (I think it dose not finally succeed), and fails to use the default irqs and ports at last. Is it that oskit10_support_l4env is not a completed port to l4env (I guess maybe it still try to allocate irqs and ports from rmgr but not l4io)? Is it possible to make the oskit drivers work with l4env? How to? "Using the OSKit as a base for L4 applications" noted that oskit10_support uses lthread_ex_regs to implement interrupt handling, and it may cause some problems. Dose oskit10_support_l4env still have this problem? Thanks! Jianjun Shen ___________________________________________________________ 雅虎免费G邮箱－No.1的防毒防垃圾超大邮箱 http://cn.mail.yahoo.com

4 8

Problem using remote-cvs
by Christoph Mueller 12 Oct '05

12 Oct '05

Hello, I tried to checkout an actual version of drops from the remote-cvs using the commands given on the website. cvs -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs login cvs -z3 -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs checkout l4 dde hello l4env It fails with the following error: [..] cvs checkout: Updating l4/tool/dice/src/parser/inc cvs checkout: failed to create lock directory for `/home/remote-cvs/CVSROOT' (/home/remote-cvs/CVSROOT/#cvs.history.lock): The file access permissions do not allow the specified action. cvs checkout: failed to obtain history lock in repository `/home/remote-cvs' What am I doing wrong? Christoph

2 1

no makefile in v4_branch?
by Matthias Lange 11 Oct '05

11 Oct '05

Hi, I've checked out both the modules "fiasco" and "preprocess" from CVS. Because I am going to work on the v4_branch of Fiasco I've only checked out the v4_branch of the fiasco module. Following the build instructions on http://os.inf.tu-dresden.de/fiasco/use.html I wasn't able to locate the Makefile in l4/kernel/fiasco. Checking out the complete module "fiasco" and later updating it with "cvs update -r v4_branch" removes this Makefile. Is this intended behavior or is this Makefile just missing in the v4_branch? Regards, Matthias.

2 1

l4-ux
by Alan Grimes 10 Oct '05

10 Oct '05

Here's wut I get when trying to compile l4-ux: (ofcourse this is a second make run...) I wish I knew how you managed to get a guest kernel to run like this anyway... I wish I knew how you figured out to get a guest kernel to run when the documentation that comes with linux sucks so badly... ################# atg@leenooks ~/source/pot $ make make -r -I"/home/atg/source/l4/kernel/fiasco/src" -f "/home/atg/source/l4/kernel/fiasco/src"/Makefile srcdir="/home/atg/source/l4/kernel/fiasco/src" "all" make[1]: Entering directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub1 make[2]: Entering directory `/home/atg/source/pot' Checking compiler config... unchanged. make[2]: Leaving directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub2 all make[2]: Entering directory `/home/atg/source/pot' ... Making entry-ia32-ux.o ... Making sighandler.o ... Making shortcut-ia32-ux.o ==> Linking kernel.image /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ld: errno: TLS definition in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a(errno.o) section .tbss mismatches non-TLS reference in boot_info-ux.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [kernel.image] Error 1 make[2]: Leaving directory `/home/atg/source/pot' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/atg/source/pot' make: *** [all] Error 2 atg@leenooks ~/source/pot $ ################# -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! http://users.rcn.com/alangrimes/

2 1

ANNOUNCE: NICTA L4-embedded API
by Gernot Heiser 05 Oct '05

05 Oct '05

National ICT Australia and the L4Ka Team are pleased to announce the release of the L4-embedded API. It is based on the X.2 API and aims to provide better support for embedded systems. Specifically, it aims to reduce complexity and memory overhead on architectures with limited resources, while keeping the API small, clean, and mostly compatible to X.2. Reference and user manuals for the new ABI are available from the NICTA L4 site http://www.ertos.nicta.com.au/Research/L4/ and from http://l4hq.org/. A release of a first compliant kernel is planned for later this month. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

Re: l4dm_mem_open call from L4Linux user process
by Julian Grizzard 05 Oct '05

05 Oct '05

All, I accidentally responded off list to this topic. Here's Adam's reply that may be helpful to others with similar questions to this thread. Adam's suggestion on where to look for example code and other comments are below. I was able to use the example code to create two linux apps, one which creates a DS and another that attaches to that DS. Julian -------- Original Message -------- Subject: Re: l4dm_mem_open call from L4Linux user process Date: Thu, 29 Sep 2005 22:05:18 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: Julian Grizzard <grizzard(a)ece.gatech.edu> References: <433ABD93.2020303(a)ece.gatech.edu> <20050929074724.GL31351(a)os.inf.tu-dresden.de> <433C3AE5.4070601(a)ece.gatech.edu> On Thu Sep 29, 2005 at 15:05:09 -0400, Julian Grizzard wrote: > Adam Lackorzynski wrote: > > Hi, > > > > On Wed Sep 28, 2005 at 11:58:11 -0400, Julian Grizzard wrote: > > > >>I've been working with the dataspace calls with the L4Env running x86 > >>Fiasco. I am trying to create a dataspace from a L4Linux user process, > >>but I am having trouble getting the program to compile. Is my Makefile > >>correct for what I am trying to do? Is there any reason I shouldn't be > >>able to link to l4dm_mem_open from a L4Linux user process? Below is my > >>source, Makefile, and compiler error message. Help much appreciated! > >> > > > > > > Umm, basically it's possible to create a new DS in an L4Linux user app, > > as it is created at your DS manager (so most likely dm_phys). This has > > nothing to do with L4Linux or the user app in the first place. > > Attaching to it is a different issue altogether! > > > > Alright, so my eventual goal would be to attach to the DS as well. So, > attaching to a DS is going to be a problem? I figured I would try a > simple case first: just create the DS. The address space of a Linux user app is handled by the Linux server, so if one starts mapping stuff in there without telling Linux it may just overmap this area as it believes it is free, or in other words, no one is mapping stuff in there (which cannot happen in native Linux, so this is ok). So now one could start telling Linux about that region. I think the cleanest way would be to hack something in L4Linux to exclude/reserve a region in an address space of a task. This has not been done yet. Something cheaper could be to mmap something and then overmap it itself, or similar. Depending on what you want to do, there's a good example in l4/pkg/loader/examples/fprov-l4/main.c where a DS is opened but the attaching is done in a way that it works, i.e. some memory in BSS is allocated and unmap, and then, at this location, a page from the DS is mapped in. Just have a look, maybe this is ok for you. > >>---------- SOURCE ---------- > >>#include <l4/dm_mem/dm_mem.h> > >>#include <l4/l4rm/l4rm.h> > >> > >>#include <l4/sys/types.h> > >>#include <l4/dm_generic/types.h> > >> > >>int main(int argc, char**argv){ > >> l4dm_dataspace_t ds; > >> void *addr; > >> > >> l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); > >> printf("hi\n"); > >> > >> return 0; > >>} > >> > >>---------- MAKEFILE ---------- > >>PKGDIR ?= ../.. > >>L4DIR ?= $(PKGDIR)/../.. > >> > >>TARGET = $(PKGNAME) > >> > >>MODE = host > > > > > > Mode 'host' has no L4 specific libs, includes etc, try 'l4linux' which > > gives you host + L4 stuff. > > > > This should basically fix your linking problem because the libs you link > > have dependencies to other libs which must be fulfilled. > > Okay, I've tried mode = l4linux. Now I get the error message below. > Looks like some libraries are still not getting pulled in. Do I need to > manually specify some L4LIBS? I tried several combinations but didn't > get anywhere. Any ideas? Whoa, looks like this was the wrong approach. This is pulling much more in which is really too low level for a Linux program. But have a look at the fprov-l4 example, it is hopefully enough for what you want to do. Cheers, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

drops-demo from hard disk
by Shakthi Kannan 04 Oct '05

04 Oct '05

Greetings! I would like to know if its possible to dump the drops-demo-floppy.img to a primary partition of the hard disk and boot from it? I tried dumping the image to /dev/hdb3 using dd: dd if=drops-demo-floppy.img of=/dev/hdb3 bs=512 count=2880 The above worked fine. I tried to boot it from grub in the MBR using: root (hd0,3) chainloader +1 I get " root (hd0,3) Filesystem type unknown, partition type 0x83 chainloader +1 GRUB" Do we need any filesystem support in drops-demo-floppy.img for it? My GNU/Linux boot entry is: " root (hd0,2) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb3 ro single initrd /boot/initrd-2.4.27-2-386 boot " My partitioning scheme is: /dev/hdb1 - fat32 (data) /dev/hdb2 - swap /dev/hdb3 - linux /dev/hdb4 - 1.44 drops image Any suggestions? Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

env.ipc_error: unknown
by Shakthi Kannan 30 Sep '05

30 Sep '05

Greetings! I have been working on the BID tutorial in writing the hiworld example. I was able to complete the exercise :) I just found one compilation error, in "4.3 Client helper library", where it said no member ipc_error for env. Declaration is as follows: CORBA_Environment env = dice_default_environment; One usage in the example is: return -env.ipc_error; I checked l4/tool/dice/include/dice/dice-corba-types.h and for l4x2 version, ipc_error is declared inside a _p union. Hence, the usage of: env._p.ipc_error worked fine. Is that correct? I tested hiclient and hiserver replacing demo-drops images with my compiled ones, and it worked fine. My documentation and the source code can be viewed from: http://www.shakthimaan.com -> fiasco Regards, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

About driver stubs for L4Linux
by Jianjun Shen 29 Sep '05

29 Sep '05

Hello, I try to run multiple L4Linux instances. Dose L4Linux-2.4 or L4Linux-2.6 implement the driver stubs for oshkosh, ide driver and bmodfs? Where can I find them? Thanks! Wei ___________________________________________________________ 雅虎邮箱超强增值服务－2G超大空间、pop3收信、无限量邮件提醒 http://cn.mail.yahoo.com

2 1

l4dm_mem_open call from L4Linux user process
by Julian Grizzard 29 Sep '05

29 Sep '05

All, I've been working with the dataspace calls with the L4Env running x86 Fiasco. I am trying to create a dataspace from a L4Linux user process, but I am having trouble getting the program to compile. Is my Makefile correct for what I am trying to do? Is there any reason I shouldn't be able to link to l4dm_mem_open from a L4Linux user process? Below is my source, Makefile, and compiler error message. Help much appreciated! ---------- SOURCE ---------- #include <l4/dm_mem/dm_mem.h> #include <l4/l4rm/l4rm.h> #include <l4/sys/types.h> #include <l4/dm_generic/types.h> int main(int argc, char**argv){ l4dm_dataspace_t ds; void *addr; l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); printf("hi\n"); return 0; } ---------- MAKEFILE ---------- PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = $(PKGNAME) MODE = host SYSTEMS = x86-l4v2 x86-l4x0 # list your .c files here SRC_C = main.c LIBCINCDIR = $(addprefix -I,$(L4INCDIR)) # if your server implements the server side of an idl defined in an idl-file # of your package, list the idl file name(s) here (no path needed) SERVERIDL = # list additional library paths and libraries here LIBS = -ldm_generic -ldm_mem include $(L4DIR)/mk/prog.mk ---------- COMPILER ERROR ---------- jgrizza@tomato:~/build_2.6.01/l4/pkg/create_ds/server/src$ make PWD=/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -c -DRAM_BASE=0x0 -DUSE_OSKIT=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/l4v2 -I../../../../../include/x86 -I/home/jgrizza/build_2.6.01/drops/include/x86 -I../../../../../include -I/home/jgrizza/build_2.6.01/drops/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c -o main.o /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c: In function `main': /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:12: warning: implicit declaration of function `printf' /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:9: warning: unused variable `addr' ==> Linking create_ds LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=create_ds GENDEP_BINARY=ld gcc -o create_ds main.o -L../../../../../lib/x86_586/l4v2 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586 -L../../../../../lib -L/home/jgrizza/build_2.6.01/drops/lib -ldm_generic -ldm_mem ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xba): In function `l4dm_mem_open': /home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:87: undefined reference to `LOG_logL' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xff):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:62: undefined reference to `l4env_get_default_dsm' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0x12b):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:65: undefined reference to `LOG_logL' collect2: ld returned 1 exit status make[1]: *** [create_ds] Error 1 make[1]: Leaving directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' make: *** [OBJ-x86_586-l4v2] Error 2 Thanks! Julian

2 1

names memory overlap error
by Shakthi Kannan 28 Sep '05

28 Sep '05

Greetings! Just started playing around with fiasco and l4env. I checked out l4env and hello from CVS, which obtained all the required files. I was able to compile it on my x86 Thinkpad (T41) running Debian Sarge 3.1r0a. I've added an entry in boot/grub/menu.lst as follows: title DROPS/Fiasco u-kernel kernel (hd0,0)/boot/fiasco/rmgr -sigma0 module (hd0,0)/boot/fiasco/main -noserial -nowait -nokdb module (hd0,0)/boot/fiasco/sigma0 module (hd0,0)/boot/fiasco/names module (hd0,0)/boot/fiasco/log module (hd0,0)/boot/fiasco/dm_phys module (hd0,0)/boot/fiasco/hello On boot, I get the following output: " RMGR: Starting tasks #OS: loading "(hd0,0)/boot/fiasco/names" from 0022b000 - 002341a4 to [ 02240000 - 00246b52 The module 02: 02240000 - 00246b52 : (hd0,0)/boot/fiasco/names overlaps with module loaded by bootloader at 00100000 - 001ca240: Rmgr 02: 0022b000 - 002341a4: (hd0,0)/boot/fiasco/names 03: 00235000 - 0023d324: (hd0,0)/boot/fiasco/log 04: 0023e000 - 00252584: (hd0,0)/boot/fiasco/dm_phys 05: 00253000 - 0025d7ef: (hd0,0)/boot/fiasco/hello The reason for this error message is that the modules as loaded by grub interface with their final position as defined by the linker. Most often you can solve this problem by inserting the command "modaddr 0x02000000" immediately as next line after the "kernel=" line of your menu.lst. Note that you have to use a special version of GRUB which is available from http://os.inf.tu-dresden.de/drops/download.html. Return reboots, "k" enters L4 kernel debugging. " I already have grub installed in the MBR of the hard disk, and I don't have a floppy drive in the laptop. 1. Is there any other way I can get these modules loaded and tested? Of course, hello module does not require the names, log, dm_phys modules. It runs fine though with rmgr, main and sigma0. 2. I am particularly interested in device drivers. Is there any documentation that covers these in DROPS other than using Linux device drivers? I'd appreciate any help in this regard. Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 6

[ANN] Fiasco 1.2 released
by Adam Lackorzynski 26 Sep '05

26 Sep '05

The operating system's group at Technische Universität Dresden is pleased to announce the release of version 1.2 of the Fiasco L4 microkernel. Since the last release Fiasco has significantly matured and is now thought to be the most stable version available. For a comprehensive list of changes please consult the CHANGES file in the distribution. Highlights are the integration of scheduling extensions targeted at real-time applications, better support for paravirtualised systems as well as numerous bug-fixes. The Fiasco kernel currently runs on the x86 and Linux/x86 platforms (UX) as well as various ARM platforms. All platform implementations are believed to be equally stable. More information is available at the Fiasco website at http://os.inf.tu-dresden.de/fiasco/ Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Did not find VBE info block
by Shakthi Kannan 26 Sep '05

26 Sep '05

Greetings! I am trying to get the console using l4env and fiasco on an old x86 desktop. Is it like the bash shell? Images have been compiled from CVS sources. All images are booted from the grub present in the demo floppy. The grub entry is as follows: kernel (fd0)/l4/v2/rmgr -sigma0 modaddr 0x01500000 kernel (fd0)/l4/v2/main -noserial -nowait -nokdb kernel (fd0)/l4/v2/sigma0 kernel (fd0)/l4/v2/names kernel (fd0)/l4/v2/log kernel (fd0)/l4/v2/dm_phys kernel (fd0)/l4/v2/con The output that I get while booting is as follows: " con | OSKit support: using 128 KB at 0x00002000 as heap con | Characters size is 8x14, font has 256 characters con | vc_init_gr (): con | [8.2] l4con/server/src/vc.c: 315: vc_init_gr(): con | Did not find VBE info block in multiboot info con | Perhaps you have to upgrade GRUB, RMGR or oskit10_support con | GRUB has to set the video mode with the vbeset command con | con | Alternatively, try passing the --vbemode=<mode> switch con | ----PANIC, 'g' for exit " By console, does it correspond to serial port output or the VGA display? The desktop is a Sony Trinitron multiscan 15sx display. Any suggestions/ideas would be useful, Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 5

Problems porting L4Linux 2.4 module to 2.6
by Derick Swanepoel 22 Sep '05

22 Sep '05

Hi, I'm trying to convert a custom kernel 2.4 module to 2.6. The most serious problem I'm having is that there are now some unresolved symbols with 2.6: *** Warning: "l4rm_detach" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "kmalloc" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4rm_do_attach" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4env_err_ipcstrings" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4lx_thread_shutdown" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4lx_thread_create" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4_sleep" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "names_waitfor_name" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! I see that there is no l4_ksyms.c in l4linux 2.6 like there was in 2.4. Secondly, I get more unresolved symbols if the objects that are linked are specified at the end of the command line instead of the beginning (linking succeeds in both cases, however). The kernel build system puts the objects at the end while the DROPS build system puts them at the beginning. Does anyone have an idea why two otherwise equivalent linking commands would cause such different behaviour depending on the position of the object arguments? Here are the two command lines (the paths are slightly different because the kernel build system always outputs to the source directory: DROPS: gcc -o test_module.o test_dev.o main.o test_dm-client.o -r -nostdlib -nostartfiles -L../../../../../lib/x86_686/l4v2 -L/home/drops/DROPS-20050908/drops/lib/x86_686/l4v2 -L../../../../../lib/x86_686 -L/home/drops/DROPS-20050908/drops/lib/x86_686 -L../../../../../lib -L/home/drops/DROPS-20050908/drops/lib -T../../../../../lib/x86_686/main_rel.ld -ltest_lxk -ldm_generic -ldm_phys -ldm_mem kernel: gcc -r -nostdlib -nostartfiles -L/home/drops/DROPS-20050908/drops/lib/x86_686/l4v2 -L/home/drops/DROPS-20050908/drops/lib/x86_686 -L/home/drops/DROPS-20050908/drops/lib -T/home/drops/DROPS-20050908/l4/lib/x86_686/main_rel.ld -ltest_lxk -ldm_generic -ldm_phys -ldm_mem OBJ-x86_686-l4v2/mesg_dm-client.o -o test_module.o test_dev.o main.o Thanks, Derick

2 4

Problem with hybrid L4Linux task
by Mathias Krause 19 Sep '05

19 Sep '05

Hello Hackers, I've got a problem with a hybrid Linux Task. I want to create a little tool to tranfser data between two L4Linuxes easily. A tool similar to the famous netcat but using IPC instead of UDP/TCP. So far so good. Server is listen for client and client is sending data to the server (using long IPC transfering data as dwords). The problem is that the data doesn't arrive at the server task. There only an empty IPC message gets received (no IPC error). After I've played around a while with debug messages I got strange results. Using debug messages (simple printf()) inbetween and the transfer succedes! Digging a little deeper got me to the point that it must be a problem with the compiler. Using 'gcc -O0' generates working code too - 'gcc -O2' doesn't. Trying another compiler (gcc version 4.0.1 (Debian 4.0.1-2)) with -O2 got me also working code. So my question is if really my gcc (version 3.3.5 (Debian 1:3.3.5-13)) is broken or the includes under l4/l4sys/.../ipc.h. Maybe the inline assembly isn't that clean? But just a guess. My GNU assembly knowlegde isn't that good. Greets, Mathias PS: I'm runing Debian sarge over here.

2 4

Compiling DROPS' dietlibc on FreeBSD
by Julian Stecklina 15 Sep '05

15 Sep '05

Hello, after changing minimal parts of dietlibc's build procedure, I get as far as cd pkg/dietlibc ; gmake actually doing something but it fails with the following error: ... Compiling lib/__v_printf.o LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so GENDEP_TARGET=lib/__v_printf.o GENDEP_BINARY=cc1 gcc33 -c -nostdinc -DRAM_BASE=0x0 -DUSE_DIETLIBC=y -DSYSTEM_x86_686 -DARCH_x86 -DCPUTYPE_686 -DL4API_ -I../include -I.. -I../../../idl/OBJ-x86- -I/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i686 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c -o lib/__v_printf.o /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:2:20: stdarg.h: No such file or directory In file included from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: ../dietstdio.h:12:20: stdarg.h: No such file or directory In file included from ../dietstdio.h:52, from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: ../include/stdio.h:7:20: stdarg.h: No such file or directory In file included from ../dietstdio.h:52, from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: The include directories look bogus, but I am quite puzzled where they come from. Maybe my directory layout is somehow different from what is expected? Any hint is greatly appreciated. Regards, -- Julian Stecklina Lisp nearing the age of 50 is the most modern language out there. GC, dynamic, reflective, the best OO model extant including GFs, procedural macros, and the only thing old-fashioned about it is that it is compiled and fast. -- Kenny Tilton, comp.lang.python

4 9

[Fwd: Re: Inspect L4Linux Memory]
by Julian Grizzard 15 Sep '05

15 Sep '05

Forgot to copy to list...message below -------- Original Message -------- Subject: Re: Inspect L4Linux Memory Date: Tue, 13 Sep 2005 14:12:14 -0400 From: Julian Grizzard <grizzard(a)ece.gatech.edu> To: Marcus Voelp <voelp(a)os.inf.tu-dresden.de> References: <432214B5.8010109(a)ece.gatech.edu> <43225D54.7040009(a)os.inf.tu-dresden.de> Marcus and all, I like option two better: sharing the dataspace that provides L4Linux with memory. After studying docs under l4/pkg/dm_phys/doc/dm_phys/html, seems like first I need to make an l4dm_share call from the L4Linux server. Then, I should be able make an l4dm_map call from the isolated L4 task. Does this sound like the right general approach? Also, I have a question about the examples under l4/pkg/dm_phys/examples. Take list_ds. There is a call to "if_l4dm_generic_list_call". Where is this call defined? It's not clearly locatable in the API? Is this an IDL thing? I'm not too familiar with IDL. Thanks! -Julian Marcus Voelp wrote: > Hi, > there are actually two nice ways how you can access L4Linux kernel > memory. The first is to install a driver to L4Linux which creates an L4 > thread that in turn would read out the memory when requested to do so. > The second is mapping the L4Linux memory to your external observer by > sharing the dataspace that provides L4Linux with memory. > > The first solution obviously is not suited when reading out much data > and you also rely on the thread to live (i.e., if Linux crashes there is > the chance that the driver thread crashes as well). The second solution > provides a faster read access and survives also kernel crashes. > > Regards > Marcus > > Julian Grizzard wrote: > >> Hi all, >> >> I am running L4Linux 2.6 on Fiasco using L4Env. I would like to build >> an isolated L4 task that can inspect the contents of the L4Linux task >> state. Any pointers on the best way to do this? Conceivably, I could >> map the contents of the L4Linux task into my isolated L4 task to read >> the memory, but I'm not sure the best way to do this. >> >> Thanks! >> >> -Julian >> >> _______________________________________________ >> l4-hackers mailing list >> l4-hackers(a)os.inf.tu-dresden.de >> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >> >> >

3 2

Inspect L4Linux Memory
by Julian Grizzard 10 Sep '05

10 Sep '05

Hi all, I am running L4Linux 2.6 on Fiasco using L4Env. I would like to build an isolated L4 task that can inspect the contents of the L4Linux task state. Any pointers on the best way to do this? Conceivably, I could map the contents of the L4Linux task into my isolated L4 task to read the memory, but I'm not sure the best way to do this. Thanks! -Julian

2 1

Re: Reboot does not work anymore!
by Derick Swanepoel 08 Sep '05

08 Sep '05

Very sorry, this should've gone to the list. ---------- Forwarded message ---------- From: Derick Swanepoel <dswanepoel(a)gmail.com> Date: 08-Sep-2005 12:21 Subject: Re: Reboot does not work anymore! To: Frank Mehnert <fm3(a)os.inf.tu-dresden.de> On 8/17/05, Frank Mehnert <fm3(a)os.inf.tu-dresden.de> wrote: > On Wednesday 17 August 2005 15:48, Leon Brits wrote: > > > Should not does any matter. But how do you set the video mode, via GRUB > > > vbeset of via --vbemode parameter of l4con? > > > > grub > > Hmm. Very strange. When you reboot via the l4con console you most probably > mean the pkg/loader/example/run program. Could you please disassemble that > binary > > objdump -ld loader/example/run/OBJ-x86_586-l4v2/run | less > > and search for pc_reset, right? That function should come from oskit10 and > we did not change anything there. Hi, I'm having the same problem (CVS 20050829). Rebooting does not work from "run" or from JDB. It gets as far saying: Return reboots, "k" enters L4 kernel debugger... Rebooting. Shutting down... but then nothing happens. This is on a Pentium 4 machine. Strangely, however, it works on a Xeon. For what it's worth, here is the disassembled pc_reset(): 013082f0 <pc_reset>: pc_reset(): ../kern/x86/pc/reset.c:30 13082f0: 55 push %ebp 13082f1: 89 e5 mov %esp,%ebp 13082f3: 53 push %ebx 13082f4: 50 push %eax 13082f5: bb 63 00 00 00 mov $0x63,%ebx ../kern/x86/pc/reset.c:34 13082fa: a1 ec 05 31 01 mov 0x13105ec,%eax 13082ff: 66 c7 80 72 04 00 00 movw $0x1234,0x472(%eax) 1308306: 34 12 ../kern/x86/pc/reset.c:39 1308308: 83 ec 0c sub $0xc,%esp 130830b: 68 fe 00 00 00 push $0xfe 1308310: e8 1b 00 00 00 call 1308330 <kb_command> ../kern/x86/pc/reset.c:37 1308315: 83 c4 10 add $0x10,%esp 1308318: 4b dec %ebx 1308319: 79 ed jns 1308308 <pc_reset+0x18> ../kern/x86/pc/reset.c:45 130831b: 0f 01 1d 9e 04 31 01 lidtl 0x131049e ../kern/x86/pc/reset.c:46 1308322: cc int3 1308323: 8b 5d fc mov 0xfffffffc(%ebp),%ebx 1308326: c9 leave 1308327: c3 ret Thanks, Derick

2 1

Sawmill's dataspaces and the Hurd's physmem
by Neal H. Walfield 06 Sep '05

06 Sep '05

During my presentation of the design of the Hurd on L4 to the Dresden group, Lars Reuther asked me if I had considered Sawmill's dataspace model and if so why I had rejected it. My answer was that we want to be able to catch any errors at the time of data acquisition and that relying on a file system server to provide a mapping to the data does not guarantee this: a malicious server can unmap mappings and refuse to remap them; or if the server is shorter lived than the client, the the data becomes inaccessible to the client when the server exits. Lars asked for more details. Unfortunately, I failed to provide a coherent and complete argument: my problem was mainly that I came to this conclusion fairly early in the design process and had since forgotten too many details of Sawmill's architecture to reconstruct my argumentation. I've recently revisited some related issues and am now in a position to better answer Lars's question. My primary reference for the Sawmill framework is [1]. I think I may be able to best explain the problem with an illustration: consider a server providing access to a file system backed by a disk. In the Sawmill dataspace model [1], the file system server is a dataspace manager which likely provides a dataspace for each file. When a task wants to use a file, it first identifies the dataspace associated with the file (e.g. gets a capability to the file from the DM) and attaches it to its address space (e.g. tells its pager to associate a portion of the VM with the capability). "After an attach, the region mapping forwards all page fault requests in that region to the dataspace manager. The dataspace manager resolves the faults with map or grant operations." I understand this to mean that a client depends on a DM to: - provide mappings to data - provide resources backing the data When a client requests some data from a dataspace, the DM provides a mapping to the client. The client can proceed to use the data, however, at any point, the server could cause the mapping to be unmapped and possibly render the data inaccessible. The implication is that the client must either trust the server to always provide the mapping or be prepared to recover should the data disappear. The latter approach can be simplified by making a physical copy of data before committing to using it (which can be done by interposing a second DM between the DM and the client). General use of this tactic means a lot of cycles will be spent copying bytes and a reduction in the amount of physical memory sharing in the system. DMs appear to use their own resources to fetch and store data as well as to hold data (neither [1] nor [2] mentions any mechanism for the client to specify to the DM what memory/data space to read data into). I assume that the normal mode of operation is that a file system DM has a certain amount of physical memory available from a "physical memory" DM which it uses to hold data from backing store. Once that memory is exhausted, it must choose some page to evict. There are several problems with this model: because DMs allocate resources on behalf of clients resources are allocated with the priority of the DM and resource accounting is extremely difficult. We know this from our experience with the Hurd on Mach. Moreover, the DM controls the paging policy; not the clients who are actively using the memory. To control the availability of memory, it would seem that a client would again have to copy the data. [ Physmem DM ] | v [ FS DM ] | v [ client ] The framework that I have developed for the Hurd avoids these dependencies on the file system servers. The physical memory manager ("physmem") is part of the TCB. physmem provides capabilities to so-called containers which identify memory reservations (either specific, e.g. a specific set of frames, or general, e.g. a specific number of frames). Given a container capability, the holder can map the contents or logically copy the contains to or from a second container. When a task wants to read data from a file, it passes a container capability to the file system server. The file system server stores the data in the container (if it already read it into memory then it can logically copy it). Then it returns to the client. If the task wants a mapping to the data, it requests one from physmem. Thus, tasks on the Hurd do not depend on file system server to provide mappings. After the read is complete, the task knows that the data is either available or not available. If the file system server exits, this does not affect the data that the client has. [ physmem ] / \ |_ _| [ client ] [ FS ] Because the client passes containers to the server, the server does not allocate memory to store the data on behalf of the client. (The server may need other resources such as CPU time, I/O bandwidth and state, however, we have other provisions for that.) Thus memory allocations are directly attributed to the client which is vital to the correct functioning of accounting. Also, when the client has exhausted its memory quota, it must free some memory before it can allocate a container with the required reserve. Thus, clients fully control their own paging policy. One of the goals of the Hurd framework is to minimize the number of dependencies that a client has on the behavior of servers. This is important to us because clients often interact with other users's servers which may be malicious. Another goal is to more directly link consumers of resources with resource allocators. Our observation is that many applications are hurt due to policies such as the eviction scheme imposed by the OS. Moreover, applications such as garbage collectors and multimedia applications could benefit from knowing how much real resource is actually available to them. (Applications should work in harmony with the mechanisms provided to them and the policies imposed on them; they should not have to work around them.) Thanks. I have tried to be as concise as possible which means I may have missed some details. I am particularly interested in the thoughts of the Sawmill and DROPS developpers. Neal [1] http://l4ka.org/publications/2001/sawmill-framework.pdf [2] http://os.inf.tu-dresden.de/l4env/doc/l4env-concept/l4env.pdf

4 6

DROPS build success on FreeBSD
by Julian Stecklina 04 Sep '05

04 Sep '05

Hello, I managed to compile most (the documentation fails with latex errors) of DROPS using the attached patch on FreeBSD 5.4. Notes on how to build drops on L4 are attached as well. Notable difficulties in porting: * bash assumed to be in /bin/ (solved with sed) * assuming Linux-style /proc in gendep * assuming dynamically-linked gcc It might be worthwile to make kernel/fiasco/src/Makeconf include mk/Makeconf to avoid redundancy. I think the whole build process would be quite portable with some autoconf magic and with gendep removed. Also I did not test the result. Maybe tomorrow. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

1 1

gendep on FreeBSD
by Julian Stecklina 03 Sep '05

03 Sep '05

Hello, in my quest to get the Fiasco tree buildable on FreeBSD I encountered the following problem (this is with gendep compiled with VERBOSE=1) [...] echo BID_LIBGENDEP=/home/blitz/src/l4/tool/gendep/libgendep.so >>./.Makeconf.bid.converted; echo 'BUILD_PIC += $(BUILD_LOADER_PICS)' >>>>./.Makeconf.bid.converted set -e; X="tmp.$$$RANDOM.c" ; echo 'int main(void){}'>$X ; rm -f $X.out ; LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so GENDEP_SOURCE=$X GENDEP_OUTPUT=$X.out gcc33 -c $X -o $X.o; test -e $X.out; echo INT_CPP_x86_NAME=`cat $X.out` >>./.Makeconf.bid.converted; rm -f $X $X.{o,out}; fopen(/proc/self/cmdline) real_fopen(/proc/self/cmdline) gendep: Cannot resolve fopen(): Unknown error: 0 It seems that RTLD magic is somehow broken, but I cannot say how... if someone has a hint, I am all ears. My patches to gendep are attached. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

1 1

Fiasco CVS repository
by Julian Stecklina 03 Sep '05

03 Sep '05

Hello, I have some problems with the CVS repository for Fiasco: cvs diff: failed to create lock directory for `/home/remote-cvs/l4/tool/twiddler' (/home/remote-cvs/l4/tool/twiddler/#cvs.lock): A file or directory in the path name does not exist. cvs diff: failed to obtain dir lock in repository `/home/remote-cvs/l4/tool/twiddler' cvs [diff aborted]: read lock failed - giving up Same goes with 'update' always in the twiddler directory. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

2 2

RE: Critics on L4 (NOT Re: shared memory Beispiel?)
by yuan Darwin-r62832 02 Sep '05

02 Sep '05

Hi, >Hi L4Ka::Pistachio developers, > >I have read the source code of L4Ka::Pistachio-0.4. & found that some >features defined in L4 eXperimental Kernel Reference Manual Version X.2 Revision 5 hasn't been implemented yet. For example, appoint redirector by SpaceControl, IO port mapping, etc. > > Please understand that both Pistachio and Fiasco are research prototypes and that the L4 eXperimental Kernel Reference Manual is indeed EXPERIMENTAL which means that it may change unnoticed and which also means that the prototypes may differ from the specification. The missing features that you state are published, e.g., at http://l4ka.org/projects/pistachio/ia32/ under the section Missing Features / Known Bugs for the Pistachio kernel , respectively at http://os.inf.tu-dresden.de/fiasco/status.html for Fiasco. [Darwin Yuan] Thanks for your information, I started to learn L4 just 1 month. A totally junior. Anything I was wrong, pls correct me. >I tried to checkout the newest source code from CVS, & the CVS server >cvs.l4ka.org couldn't be reached. > > I had no problems reaching the server. Though I cannot confirm that it was up all the time. [Darwin Yuan] Thanks, I'll try later. >When those features are going to be implemented? > Fiasco implements IO Flexpages. Neither Redirectors nor Clans and Chiefs are currently implemented in Fiasco and probably never will. I cannot speak for plans regarding Pistachio. [Darwin Yuan] I didn't read the source code of Fiasco. However, from the documents I got from its website, I found that Clans & Chiefs was implemented in its kernel ( It might be removed now). But I don't think it's a good design that this policy was involved in L4 kernel, now that L4 claims it's a real microkernel. However, I think those kind of policies could be implemented outside kernel. Therefore, I think Redirector is a good mechanism to achieve those kind of policies. That's why I think redirector is very important for implementing a flexible system on L4. >Now that those features are very important for implementing a flexible >OS on L4 u-kernel. > > Both redirectors and IO flexpages are not essential to get a system up and running. Their purpose is to control and restrict communication between threads respectively to prevent a thread from reading / writing IO-ports. Feel free to implement those features if you need them. [Darwin Yuan] Yes, That's true. However, a real system should makes peripheral equipment work. IO Fpage is very essential for implementing hardware driver. Can you elaborate on why you thing missing these features prevents someone building a flexible OS on L4? [Darwin Yuan] As mentioned above. >Seems that there are so many differences between L4Ka::Pistachio and >Fiasco. Is there a stardard L4 specification? > There is a standard L4 Specification: L4-V2 by Jochen Liedtke. Also there is the eXperimental specification you already found which is the defacto standard for L4-V4 kernels. The main difference between Pistachio and Fiasco is that the former implements L4-V4, the latter implements L4-V2 whereby some experimental features have been incorporated into Fiasco to better suite our user level software's needs. As you will see Fiasco already implements some parts of the L4-V4 specification. [Darwin Yuan] I see. Thanks. >I think L4Ka::Pistachio is more clean & flexible, why Fiasco put so >many complicated & inflexible policies inside L4 kernel? > > Which policies are you referring to? Can you elaborate on these points? [Darwin Yuan] For example, Clans & Chiefs. Also, I think "Task" is a redundant abstract/concept, "Address Space" is a much better one. By "Thread" & "Address Space", L4Ka::Pistachio makes the abstract very refined, and allows to construct very flexible system. All together, the APIs of X.2 is much better than X.0. >BTW, has any OS or system been built on L4Ka::Pistachio? As I know, >L4-Linux is built on Fiasco, but I don't like its design. I hope I can >get a reference system based on L4Ka::Pistachio. > > > Lets see, there is L4 Linux which runs on both Fiasco and Pistachio, L4 Env, Drops runs on Fiasco, Kenge, Iguana and Wombat on Pistachio. Also there is Mungi, Perseus, L4 Hurd, etc. Have a look at l4hq.org and you may find out much more. [Darwin Yuan] Thanks for your information. Why don't you like the design of L4Linux or do you mean Fiasco? [Darwin Yuan] Actually, I don't like the APIs & mechanism of Fiasco. Now that L4Linux is based on those APIs & mechanism, I don't like this version of L4Linux. Some more final words: It is common practice on mailing lists to start a new topic if you are referring to a totally different topic. [Darwin Yuan] Honestly, I never use any public mailling list before:(. 'cause this original mail is the first mail I got from this mailing list, I replied it. Someone else has told me about that. Thanks anyway. Best regards Marcus -- Marcus Völp TU-Dresden Department of Computer Science Institute for System Architecture Tel: +49 (351) 463-38350 Fax: +49 (351) 463-38284

5 5