[06:48] <tseliot> apw: are you around?
[06:50] <smb> tseliot, Only if suffering from insomnia
[06:51] <tseliot> smb: that would make the two of us ;)
[06:51] <smb> tseliot, Heh, yeah. Somehow I fell out of bed early today
[06:52] <tseliot> it is rather annoying...
[06:54] <smb> At least my office is less hot this morning. 
[07:45]  * apw yawns
[07:49] <RAOF> BEES!
[07:49]  * smb gets second cup of coffee
[07:49] <RAOF> Time for another steaming cup of bees!
[07:51] <smb> A stinging start into the day. :)
[08:01] <cking> bees? the buzzy sort?
[08:04]  * ppisati grabs more coffee
[08:11] <Daviey> Morning, Please can a linux-meta for saucy be uploaded to https://launchpad.net/~kernel-ppa/+archive/pre-proposed/+packages.
[08:55] <apw> Daviey, i had ben staying away from doing that because we haven't switched yet ... and the versions in that ppa are always -0 so they self update
[08:59] <Daviey> apw: Ah, the reason i wanted it was to simply upgrading to the pre-proposed kernel.
[08:59] <Daviey> surely if you add the PPA, you want the latest?
[09:08] <apw> Daviey, yeah probabally, it isn't have we have used that PPA generally, it is more about builds
[09:08] <apw> i'll see about making an unstable branch in out meta perhaps, ick
[09:22] <Daviey> apw: thanks
[10:44] <apw> Daviey, ok it is building
[10:44] <apw> expect it in the ppa in half hour or so
[10:50] <Daviey> apw: thanks
[10:51]  * ppisati goes out for lunch
[10:52] <apw> ppisati, good plan
[10:59] <smb> apw, Depending on weather conditions... :)
[10:59] <apw> heh true
[12:40]  * apw will be dropping shortly to shift locations ...
[12:41] <rtg_> apw, going to work from your local pub ?
[12:46] <apw> rtg_, oh that would be nice
[12:46] <rtg_> apw, laundramat then ?
[12:47] <apw> in laws ... not sure if that is the saem
[12:47] <apw> closest to a local pub :)
[12:47] <rtg_> surely just as much fun
[14:32] <tseliot> apw, ogasawara, rtg_: nvidia(s), fglrx(s) and broadcom should be all set for linux 3.10
[14:32] <ogasawara> tseliot: awesome, thanks!
[14:32] <rtg_> tseliot, cool. I'll upload first thing Monday
[14:32] <tseliot> good :)
[14:33] <rtg_> Daviey, y'all ready with your dkms bits ?
[14:34] <Daviey> rtg_: The primary package is a bit more complicated than we hoped.
[14:34] <Daviey> openvswitch is going to be a real pain from what we can see
[14:34] <rtg_> Daviey, bummer
[14:35] <rtg_> Daviey, do you have any folks running saucy that'll crater if I upload a 3.10 kernel ?
[14:35] <Daviey> rtg_: James Page and I both found it to be a PITA independently, but James summarised it to upstream - http://openvswitch.org/pipermail/dev/2013-June/028822.html
[14:36] <Daviey> rtg_: Well, i don't think it's a good idea to block getting 3.10 in.  We are looking to have a cheat/compat
[14:36] <rtg_> Daviey, I have to wonder why ovs isn't in the upstream kernel
[14:37] <Daviey> rtg_: half of it is.. 
[14:37] <Daviey> They are introducing it into mainline in chewable hunks.  
[14:37] <rtg_> the half that works :)
[14:38] <rtg_> ok
[14:48] <apw> man the traffic is epic today ... sigh
[14:50] <smb> apw, Is that so unusual on a Friday where you are
[14:50] <apw> smb, this early it is yeah, but the world is full i think
[14:53] <smb> apw, Yeah, that too. Here it is not uncommon to start at 2 or 3pm as commuters from farther places move home. At least I used to be stuck in there when I was one of those a long time ago... :)
[14:56] <apw> oh no
[15:27] <jsalisbury> cking, quick pci question.  Is the value for a devices "Subsystem" set in the devices firmware?  For example the values 1000:0012 in the following lspci output:
[15:27] <jsalisbury>  01:08.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)
[15:27] <jsalisbury>         Subsystem: Device [1000:0012]
[15:33] <infinity> jsalisbury: It comes from the device, if that's what you mean.  Whether that's firmware or hardware, or whatever, depends on the device in question.
[15:34] <jsalisbury> infinity, cool, makes sense.
[15:34] <infinity> jsalisbury: (Plus, in cases like full system builds, laptops come to mind, it can be masked so, for instance, all devices in a Lenovo laptop claim to be "Lenovo" instead of "Intel" and "Atheros")
[15:34] <infinity> jsalisbury: Which can be both a good or bad thing, depending on what you hope to do with said numbers. :P
[15:35] <jsalisbury> infinity, ahh, interesting
[15:35] <jsalisbury> infinity, that is definitly something to remember so not to go down a rat hole :-)
[15:38] <infinity> jsalisbury: I suppose it may be more accurate to say that it can come from the device, or the host bridge, or the ACPI tables in the BIOS, and any higher level can override the lower levels.
[15:39] <infinity> jsalisbury: Most devices themselves won't have a subsystem ID, except when they do, some hostbridges will override, some won't, and most pre-build systems seem to override in ACPI tables, except the ones that don't. :P
[15:40] <infinity> (But it's handy for, say, isolating "intel_hda, but only on on lenovo laptops", cause you can match the device ID with the subsystem ID)
[15:40] <jsalisbury> infinity, very informative.  Thanks for the details.
[16:15]  * ppisati -> EOW
[17:02]  * henrix -> EOW
[17:17]  * rtg_ -> lunch
[18:27]  * cking -> EOW
[18:44]  * rtg_ -> EOW