site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=5m67CcxyfmMbtTZZj05gMzV0/Ww6P7vW1I7spdRBxqo=; b=IaKxPJ8ycr360moF0MSvuaqOLyO/19n+wF1iu+SZA5D54XyoYpdBoQhetjsLd+wK2C rpxEBqMFDpaJAe1LUTXmd+6F/0M0pZ87k7M+4U5Lar2aPQaU6N+2eFmrcQaA7yd9a8yf AUiBUk5ZYUliex+T3tSnWC971bl4o15RyApEY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=gHBpibPayJxWkH+MgjM4QRGJtcv159onRLzbCf7HUzW7CYUEEHPy9Y6F6IZTa/wNvr cMNjy03d2Ab9YLWOBC92k+sRVwsEZROc87DZcGEQDzt8jc66X8Q1zsFPUWilYncimwty m37580CI9+8M2o/c8HCTWRAtOMTcUbbWKRyY4= I've been looking for hours for an answer to this, please help: IO Device / kext matching is done via the Device Tree, as far as I know. And the device tree, according to Amit Singh's book, exists already before the kernel gets started. Hence, either the Open Firmware / EFI ROM or the bootloader must be creating it and pass it to the kernel, doesn't it? Since I want to see if I can patch the tree before the kernel starts matching kexts on it, I need to find the code that creates it in memory and passes it to the kernel. I've looked at the boot loader code but cannot find anything that does this. Does someone know how this actually works? -- Thomas Tempelmann, http://www.tempel.org/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com