Re: x220 notes
On Wed, 14 Mar 2012 11:24:24 -0700, matt wrote Hi, Can anyone verify that suspend/resume is now broken on x220 with latest HEAD and the KMS patches? Suspend bounce causes crash, resume beep makes modem sound and hangs, logs indicate only suspend. hw.pci.do_power_resume=0 causes no change. Damn, I can confirm that I only get a black screen on resume (after being able to quickly see my desktop appear and disappear) with kernel from 2012/03/17 and http://people.freebsd.org/~kib/drm/all.13.6.patch. Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: x220 notes
On Mon, Mar 19, 2012 at 6:25 AM, Ganael LAPLANCHE marty...@freebsd.org wrote: On Wed, 14 Mar 2012 11:24:24 -0700, matt wrote Hi, Can anyone verify that suspend/resume is now broken on x220 with latest HEAD and the KMS patches? Suspend bounce causes crash, resume beep makes modem sound and hangs, logs indicate only suspend. hw.pci.do_power_resume=0 causes no change. Damn, I can confirm that I only get a black screen on resume (after being able to quickly see my desktop appear and disappear) with kernel from 2012/03/17 and http://people.freebsd.org/~kib/drm/all.13.6.patch. With the recently posted patches to if_iwn.c. I can finally reliably suspend and resume my ThinkPad. Unfortunately, I also get a black screen. However, this is with VESA on 9-STABLE, not kib's KMS patches. Also, I have not had a chance to confirm whether USB works after the resume. I'll try some display related sysctls and check out USB when I get a chance. FWIW, the display does not come back on whether I am in console mode or X. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: x220 notes
On 03/19/12 06:25, Ganael LAPLANCHE wrote: On Wed, 14 Mar 2012 11:24:24 -0700, matt wrote Hi, Can anyone verify that suspend/resume is now broken on x220 with latest HEAD and the KMS patches? Suspend bounce causes crash, resume beep makes modem sound and hangs, logs indicate only suspend. hw.pci.do_power_resume=0 causes no change. Damn, I can confirm that I only get a black screen on resume (after being able to quickly see my desktop appear and disappear) with kernel from 2012/03/17 and http://people.freebsd.org/~kib/drm/all.13.6.patch. Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Yes, same here. I'll have to try again without the patch to see if it's Xorg/KMS or FreeBSD base that has changed. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
ABI/architecture identification for packages
Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) here is the identification I propose: arch-class-os-majorversion(-archi_specific_extension) arch can be one of the following: - x86 for i386 and amd64 (discussed with kib) - powerpc for powerpc and powerpc64 - arm - mips - sparc class may be: - 32 bits - 64 bits os will always be freebsd :) (lower case) majorversion the freebsd major version (10 9 8) achi_specific_extension currently only mips and arm are concerned, for arm could be: el_oabi eb_oabi el_eabi eb_eabi (I don't know how to get arm version or hardfp/softfp from the elf) for mips I don't know much. for ia64, I have strictly no idea what I should set. Everything is read from the elf file for example: x86-64-freebsd-10 x86-32-freebsd-8 arm-32-freebsd-10-el_oabi Please help me to improve this to get the better identification to have the best possible to determine which package can be installed where. while proposing information please tell me how to get the information (dynamically) regards, Bapt pgprvLkMjQp0L.pgp Description: PGP signature
Re: ABI/architecture identification for packages
On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) here is the identification I propose: arch-class-os-majorversion(-archi_specific_extension) arch can be one of the following: - x86 for i386 and amd64 (discussed with kib) - powerpc for powerpc and powerpc64 - arm - mips - sparc class may be: - 32 bits - 64 bits os will always be freebsd :) (lower case) majorversion the freebsd major version (10 9 8) achi_specific_extension currently only mips and arm are concerned, for arm could be: el_oabi eb_oabi el_eabi eb_eabi (I don't know how to get arm version or hardfp/softfp from the elf) Fixed thanks cognet just missing the arm version now for mips I don't know much. for ia64, I have strictly no idea what I should set. Everything is read from the elf file for example: x86-64-freebsd-10 x86-32-freebsd-8 arm-32-freebsd-10-el_oabi Please help me to improve this to get the better identification to have the best possible to determine which package can be installed where. while proposing information please tell me how to get the information (dynamically) regards, Bapt pgp60gsUuHxha.pgp Description: PGP signature
Re: ABI/architecture identification for packages
On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin b...@freebsd.org wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) arch-class-os-majorversion(-archi_specific_extension) os will always be freebsd :) (lower case) So why bother? -- Eitan Adler ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ABI/architecture identification for packages
On Mon, Mar 19, 2012 at 06:01:23PM -0400, Eitan Adler wrote: On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin b...@freebsd.org wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) arch-class-os-majorversion(-archi_specific_extension) os will always be freebsd :) (lower case) So why bother? because some people from other oses are interested in pkgng (not work started on this) because some vendors might want to change it. So I read it from the elf note section regards, Bapt pgpE66l8Oqw60.pgp Description: PGP signature
Re: ABI/architecture identification for packages
On 19/03/2012 22:04, Baptiste Daroussin wrote: On Mon, Mar 19, 2012 at 06:01:23PM -0400, Eitan Adler wrote: On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin b...@freebsd.org wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) arch-class-os-majorversion(-archi_specific_extension) os will always be freebsd :) (lower case) So why bother? because some people from other oses are interested in pkgng (not work started on this) because some vendors might want to change it. So I read it from the elf note section What about if the package happens to contain linux executables? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
hi-- looking for some help
hi i saw your email inthe following link: http://lists.freebsd.org/pipermail/freebsd-current/2011-August/026412.html im studying in portugal and in have acourse about pc networking. there i have propossed to implement exactly the same thing as you have described in your email. i would like to know if ou can give me the source code of it to take some inspiration. if not can you at least tell me briefly how that is done? or at least from where i must begin to have any idea about how that is done? or at least where i can look at some code to have some clues on how that is done? i need it to be done in c for linux i thnk you in advance for your answer best regards ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ABI/architecture identification for packages
On 03/19/12 14:35, Baptiste Daroussin wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) here is the identification I propose: arch-class-os-majorversion(-archi_specific_extension) arch can be one of the following: - x86 for i386 and amd64 (discussed with kib) - powerpc for powerpc and powerpc64 - arm - mips - sparc class may be: - 32 bits - 64 bits os will always be freebsd :) (lower case) majorversion the freebsd major version (10 9 8) achi_specific_extension currently only mips and arm are concerned, for arm could be: el_oabi eb_oabi el_eabi eb_eabi One brief comment here: the output of uname -p (arm, armeb, etc.) is meant to encode the ABI completely. All platforms with the same uname -p should be able to execute each other's binaries. Why not just a sequence of `uname -p`-`uname -s`-`uname -r` (or some subset of uname -r)? That should be enough to completely encode compatibility information on almost any operating system. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ABI/architecture identification for packages
On Mon, Mar 19, 2012 at 5:41 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 03/19/12 14:35, Baptiste Daroussin wrote: Hi all, In order to identify architectures I need to find a uniq id for every possibilities (for pkgng) here is the identification I propose: arch-class-os-majorversion(-archi_specific_extension) arch can be one of the following: - x86 for i386 and amd64 (discussed with kib) - powerpc for powerpc and powerpc64 - arm - mips - sparc class may be: - 32 bits - 64 bits os will always be freebsd :) (lower case) majorversion the freebsd major version (10 9 8) achi_specific_extension currently only mips and arm are concerned, for arm could be: el_oabi eb_oabi el_eabi eb_eabi One brief comment here: the output of uname -p (arm, armeb, etc.) is meant to encode the ABI completely. All platforms with the same uname -p should be able to execute each other's binaries. Why not just a sequence of `uname -p`-`uname -s`-`uname -r` (or some subset of uname -r)? That should be enough to completely encode compatibility information on almost any operating system. The only tricky thing is that many OSes don't agree on branding. I don't know how far bapt and crew are willing to go to make pkgng OS agnostic. Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
