March 2007 - Darwin-kernel - lists.apple.com

Re: AppleYukon
by Michael Tuexen 30 Mar '07

30 Mar '07

site_archiver(a)lists.apple.com Delivered-To: Darwin-kernel(a)lists.apple.com Thank you for the information. Best regards Michael On Mar 30, 2007, at 1:28 AM, Kevin Van Vechten wrote: - Kevin On Mar 29, 2007, at 11:08 AM, Michael Tuexen wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… An engineer familiar with the driver tells me that this message is not a real error, and can be ignored. I'm stress testing a transport layer using a MacMini (Intel) and a MacBookPro connected via a Netgear Gigabit Switch GS 108. In the Console of the MacMini the message AppleYukon: bad packet received, length 60, packet status bits: Good flow-control packet Any idea what is wrong here? A bug in the driver, the switch or something else? This email sent to site_archiver(a)lists.apple.com

1 0

Re: AppleYukon
by Kevin Van Vechten 29 Mar '07

29 Mar '07

site_archiver(a)lists.apple.com Delivered-To: Darwin-kernel(a)lists.apple.com - Kevin On Mar 29, 2007, at 11:08 AM, Michael Tuexen wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… An engineer familiar with the driver tells me that this message is not a real error, and can be ignored. I'm stress testing a transport layer using a MacMini (Intel) and a MacBookPro connected via a Netgear Gigabit Switch GS 108. In the Console of the MacMini the message AppleYukon: bad packet received, length 60, packet status bits: Good flow-control packet Any idea what is wrong here? A bug in the driver, the switch or something else? This email sent to site_archiver(a)lists.apple.com

1 0

AppleYukon
by Michael Tuexen 29 Mar '07

29 Mar '07

site_archiver(a)lists.apple.com Delivered-To: Darwin-kernel(a)lists.apple.com Dear all, Best regards Michael _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… I'm stress testing a transport layer using a MacMini (Intel) and a MacBookPro connected via a Netgear Gigabit Switch GS 108. In the Console of the MacMini the message AppleYukon: bad packet received, length 60, packet status bits: Good flow-control packet Any idea what is wrong here? A bug in the driver, the switch or something else? This email sent to site_archiver(a)lists.apple.com

1 0

Re: USBSimple Example ( Still beginner )
by Francis Derive 28 Mar '07

28 Mar '07

site_archiver(a)lists.apple.com Delivered-To: Darwin-kernel(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

USBSimple Example ( Still beginner )
by Francis Derive 27 Mar '07

27 Mar '07

site_archiver(a)lists.apple.com Delivered-To: Darwin-kernel(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: xnu-792.18.15 source
by Rick Macklem 23 Mar '07

23 Mar '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com I can also wait a while for it. (For me, not having any access to Leopard kernel sources after Leopard is released, would be disappointing.) Thanks go to Kevin (or whoever else gets the sources "opened"). rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… At 3:50 PM +0100 3/23/07, Andreas Fink wrote: That's what someone would expect if its OPEN source. Otherwise the kernel should be declared CLOSED source as its source is not revealed (or at least the difference between the released binary and the released source). Although I can understand the argument, I will simply note that I greatly appreciate being able to build a kernel from Open Sources that replaces the shipped binary. It doesn't bother me that it isn't identical to the shipped binary. This email sent to site_archiver(a)lists.apple.com

1 0

Re: xnu-792.18.15 source
by Mark F. Murphy 23 Mar '07

23 Mar '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Can we stop the lecture from self declared experts on what Open Source means? This isn't an advocacy list.... it's a technical list. mark -- --------------------------------------------------------------------------- Mark F. Murphy, Director Software Development <mailto:markm@tyrell.com> Tyrell Software Corp <http://www.tyrell.com> --------------------------------------------------------------------------- _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… At 3:50 PM +0100 3/23/07, Andreas Fink wrote: That's what someone would expect if its OPEN source. Otherwise the kernel should be declared CLOSED source as its source is not revealed (or at least the difference between the released binary and the released source). This email sent to site_archiver(a)lists.apple.com

1 0

Re: xnu-792.18.15 source
by Andreas Fink 23 Mar '07

23 Mar '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: xnu-792.18.15 source
by Michael Smith 23 Mar '07

23 Mar '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… On Mar 22, 2007, at 2:50 PM, Craig Newell wrote: On Mar 22, 2007, at 17:10 , Michael Smith wrote: Neither of these are true. In addition, you truly have no idea of the scope of the work involved to identify, scrub, validate and package the number of source code projects involved in a Darwin source release. Does this mean that you can not recompile the sources and get a kernel that will function with all the usual Mac OS X applications? I am getting tired of poor filesystem performance and I was just thinking that I might spend a weekend fixing the obvious stuff in the VFS layer. As folks have noted, it is a special concern of the kernel team that it be possible for the kernel sources to be buildable by a third party into a viable replacement for the shipped kernel binary. If you're looking at making changes to the VFS layer, and you want them to be generally useful (by this I mean picked up and used for future Darwin versions) then I'd encourage you to go ahead and design your changes, then check in with someone like Terry Lambert to get a feel for how reasonable they might be in the context of Apple's ongoing work in that area. If you just want to tweak the bits for yourself, then the only caveat I would offer is that as with drivers, many of the filesystems are implemented as plug-in modules for the kernel and you may find yourself with binary compatibility problems. This email sent to site_archiver(a)lists.apple.com

1 0

Re: xnu-792.18.15 source
by Quinn 23 Mar '07

23 Mar '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Does this mean that you can not recompile the sources and get a kernel that will function with all the usual Mac OS X applications? <http://developer.apple.com/sdk/> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… At 16:26 -0700 22/3/07, Michael Crawford wrote: On 3/22/07, Craig Newell <craign(a)ieee.org> wrote: On Mar 22, 2007, at 17:10 , Michael Smith wrote: a) the source as released is necessarily exactly the source that was used to build the product No, it will work That's right. And, incidentally, this is one of the things that introduces delay between releasing the final product and releasing the Darwin source for it. rebuilding the kernel is recommended by Apple when one wants to do source code debugging of drivers. Well, I wouldn't necessarily say "recommended". In general, if you're developing a KEXT, you can usually get by with using the Darwin source combined with the symbol files from the Kernel Debug Kit. However, there are times where it's really useful to run a kernel built from source; for example, when you want to add debugging code to the subsystem that you're plugging in to. At that point building the Darwin kernel and sliding it under Mac OS X is a fine option. This email sent to site_archiver(a)lists.apple.com

1 0