Re: non-32bit-relocation
Andrew wrote: I wrote a small assembly program to send a string to the floppy. I'm not familiar with nasm, the assembly language compiler I'm using and even less familiar with the as program. basically, other code aside, the nasm compiler says, when using -f elf, that it does not support non-32-bit relocations. Ok, I'm not an assembly expert and less familiar with 'elf' so I need some help. There are a number of assembly language resources for FreeBSD; here are a couple of the better ones: http://www.int80h.org/bsdasm/ http://linuxassembly.org/resources.html The instructions were mov es, seg buffer mov bx, [buffer] int 13h. Can anyone tell me how to do this on a FreeBSD machine? You either don't do this at all, or you use the vm86() system call to do the work in a virtual machine. In general, this will not work for this particular use, since INT 0x13 is used to do disk I/O, and the BIOS interface does not own the disk, the OS disk driver does. To do what you want to do, you should probably call the open(2) system call on the disk device from assembly, and then call the write(2) system call from assembly, instead of trying to use INT 0x13. Here's a little program to write some garbage to /dev/fd0; I call it foo.s. Don't run it against a floppy you care about. Compile it with cc -o foo foo.s; it will create a dynamically linked program, unless you tell it not to (e.g. cc -static -o foo foo.s. If you don't want crt0 involved so that you can mix C and assembly, then you should follow the link above to the first tutorial. Here's the code: # # Assembly program to write a string to the floppy # # # Here are my strings # .section.rodata # /dev/fd0 + NUL .device_to_open: .byte0x2f,0x64,0x65,0x76,0x2f,0x66,0x64,0x30,0x0 # my string .string_to_write: .byte0x6d,0x79,0x20,0x73,0x74,0x72,0x69,0x6e,0x67 # # Code goes in text section # .text .p2align 2,0x90 # main() -- called by crt0's _main() function .globl main .typemain,@function main: pushl %ebp# main is a function; this is the movl %esp,%ebp# entry preamble for a function with subl $8,%esp # no parameters addl $-4,%esp # # fd = open(char *path, int flags, int mode) pushl $0 # mode 0 (not used; callee might care though) pushl $2 # flags; 2 = O_RDWR pushl $.device_to_open# path string; must be NUL terminated call open # call open function addl $16,%esp movl %eax,%eax movl %eax,fd # system call return is in %eax (-1 == error) addl $-4,%esp # write(int fd, char *buf, int len) pushl $9 # len = 9 bytes pushl $.string_to_write # buf; does not need NUL termination movl fd,%eax # fd pushl %eax call write# call write function addl $16,%esp addl $-12,%esp # close(fd) movl fd,%eax # fd pushl %eax call close# call close function addl $16,%esp # just return... we could have called exit, but _main will do that leave ret .finish: .sizemain,.finish-main # text segment size .comm fd,4,4 # global variable 'fd' # # done. # -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Please confirm your message
Your e-mail message with the subject of Re: Application is being held because your address was not recognized. To release your message for delivery, please send an empty message to the following address, or use your mailer's Reply feature. [EMAIL PROTECTED] This confirmation verifies that your message is legitimate and not junk-mail. [ This notice was generated by TMDA/0.57 (http://tmda.sf.net/), an automated junk-mail reduction system. ] --- Enclosed is a copy of your message. Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from mx2.speakeasy.net (mx2.speakeasy.net [216.254.0.225]) by ns1.rwwa.com (Postfix) with ESMTP id 8AE1C32A4 for [EMAIL PROTECTED]; Sat, 28 Jun 2003 03:58:07 -0400 (EDT) Received: (qmail 17667 invoked from network); 28 Jun 2003 07:58:02 - Received: from unknown (HELO LION) ([211.96.237.135]) (envelope-sender [EMAIL PROTECTED]) by mx2.speakeasy.net (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED]; 28 Jun 2003 07:58:02 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Application Date: Sat, 28 Jun 2003 16:00:57 +0800 Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=CSmtpMsgPart123X456_000_0076D0FA Message-Id: [EMAIL PROTECTED] [ Message body suppressed (exceeded 5 bytes) ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TODO list?
Simon L. Nielsen wrote: On 2003.06.27 16:10:13 -0700, Joshua Oreman wrote: I currently have a lot of free time and I was wondering whether there was a TODO list of some sort for bugs that need fixing in FreeBSD. I really want to help the project, and I think such a list would make it much easier to do so. If there's no official TODO list, could someone point out some things? I know C/C++, but I'm very unfamiliar with the kernel. Great :-) There is always plenty to do. I would suggest looking at the PR system and at the 'Contributing to FreeBSD' article which can be found at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/index.html Hope you find something interesting to spend some time on. Give him a commit bit, and he can quickly grind through all the PR's that already have diff's attached to them, and have just sat there forever. All he'd need to do was verify that there was a problem that was being fixed, and the code didn't look like it would cause damage. If it ends up causing damage anyway, the fix can always be backed out later. Making send-pr actually result in code changes would probably be the most valuable thing anyone could do for the project, and it would give him a chance to read and to understand a lot of diverse code, in the process, to get up to speed on writing his own fixes for PR's without fixes attached. Just my $0.02... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB, select/poll for ucom
[...] have fun. the mindshare book is good. however, it took me a long time to get a usb 'aha' moment and understand its twisty maze was really a workable design obscured by standardese... I suspect it is a problem in the usb chipset driver for the com part. ttypoll just says 'you have data in the buffer' so for some reason the data isn't making into the tty buffer. Warner Im amazed at how some of you can write a driver based on the Spec. Docs! here is a pearl i came across reading the USB spec for 1.1, page 43 'The maximum allowable interrupt data payload size is 64 bytes or less for full-speed.' danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB, select/poll for ucom
On Sat, Jun 28, 2003 at 12:37:10PM +0300, Danny Braniss wrote: [...] have fun. the mindshare book is good. however, it took me a long time to get a usb 'aha' moment and understand its twisty maze was really a workable design obscured by standardese... I suspect it is a problem in the usb chipset driver for the com part. ttypoll just says 'you have data in the buffer' so for some reason the data isn't making into the tty buffer. Warner Im amazed at how some of you can write a driver based on the Spec. Docs! here is a pearl i came across reading the USB spec for 1.1, page 43 'The maximum allowable interrupt data payload size is 64 bytes or less for full-speed.' The device will tell you his personal limits for the given endpoint. See wMaxPacketSize in usb_endpoint_descriptor_t. The specs only tell you that a device can't tell 64 byte as the maximum for an interrupt endpoint. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TODO list?
On Sat, Jun 28, 2003 at 08:27:25PM +0400, Maxim Konovalov had the gall to say: On Sat, 28 Jun 2003, 10:10-0400, Joseph Holland King wrote: heh, i must say that without a commit bit its almost impossible to get any of the pr's closed, even ones that are five years old with a fix attached. for instance? this had a fix to begin with, and has a new fix now: Re: kern/23173: read hangs in linux emulation http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173 two people have claimed that this should be closed: Re: i386/20495: 4.1-STABLE and 4.1-RELEASE: keyboard doesn't work after booting http://www.FreeBSD.org/cgi/query-pr.cgi?pr=i386/20495 this one had a patch orginally but suspended and never submitted: Re: bin/2938: Add -b, -l, and -f options to du(1) http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/2938 these are just the ones that after 8 months to a year of me (and other people) sending emails about still have not seen activity. -- Joseph Holland King [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TODO list?
On Sat, 28 Jun 2003, 14:10-0400, Joseph Holland King wrote: On Sat, Jun 28, 2003 at 08:27:25PM +0400, Maxim Konovalov had the gall to say: On Sat, 28 Jun 2003, 10:10-0400, Joseph Holland King wrote: heh, i must say that without a commit bit its almost impossible to get any of the pr's closed, even ones that are five years old with a fix attached. for instance? this had a fix to begin with, and has a new fix now: Re: kern/23173: read hangs in linux emulation http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173 Assigned to maintainer. two people have claimed that this should be closed: Re: i386/20495: 4.1-STABLE and 4.1-RELEASE: keyboard doesn't work after booting http://www.FreeBSD.org/cgi/query-pr.cgi?pr=i386/20495 Closed. this one had a patch orginally but suspended and never submitted: Re: bin/2938: Add -b, -l, and -f options to du(1) http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/2938 Closed. -- Maxim Konovalov, [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TODO list?
On Sat, Jun 28, 2003 at 10:50:17PM +0400, Maxim Konovalov wrote: On Sat, 28 Jun 2003, 14:10-0400, Joseph Holland King wrote: On Sat, Jun 28, 2003 at 08:27:25PM +0400, Maxim Konovalov had the gall to say: On Sat, 28 Jun 2003, 10:10-0400, Joseph Holland King wrote: heh, i must say that without a commit bit its almost impossible to get any of the pr's closed, even ones that are five years old with a fix attached. for instance? this had a fix to begin with, and has a new fix now: Re: kern/23173: read hangs in linux emulation http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173 Assigned to maintainer. I'm not the maintainer, but I'll commit the patch in a couple of longish minutes. An MFC will happen sometime next week. Feel free to ping me at the end of next week if it hasn't been MFC'd by then. FYI, -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TODO list?
Aloha! Short comment... Marcel Moolenaar wrote: On Sat, Jun 28, 2003 at 10:50:17PM +0400, Maxim Konovalov wrote: On Sat, 28 Jun 2003, 14:10-0400, Joseph Holland King wrote: this had a fix to begin with, and has a new fix now: Re: kern/23173: read hangs in linux emulation http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173 Assigned to maintainer. I'm not the maintainer, but I'll commit the patch in a couple of longish minutes. An MFC will happen sometime next week. Feel free to ping me at the end of next week if it hasn't been MFC'd by then. Pretty impressive, just by asking about how to contribute, Joshua Oreman have caused one commit of a fix from a PR and the closing of two other PRs. ;-) Would it be productive/meaningful if one were to browse through the PR db, check/verify open PRs with fixes and report back to this list with looks good fixes so that they then could be commited in the same way as the three PRs reported by Joseph Holland King? -- Med vänlig hälsning, Cheers! Joachim Strömbergson Joachim Strömbergson - ASIC designer, nice to *cute* animals. snail: phone: mail web: Sävenäsgatan 5A+46 31 - 27 98 47 [EMAIL PROTECTED] 416 72 Göteborg+46 733 75 97 02 www.ludd.luth.se/~watchman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Is GNATS broken ??
Hi all, Sorry for off topic, but since 5 days I am trying to send a PR with change request and included patch to [EMAIL PROTECTED] using send-pr. Today I made a resubmission, steel without any success. The article related to problem reporting (on FreeBSD site) states that I should get an auto-email with trouble ticketing number from GNATS system after I submitted the problem. In both cases I didn't get any trouble ticket number. Can please somebody tell me wheter the GNATS system is OK and if somebody managed to submit a problem report last 5 days? P.S. I CC-ed the same problem report to my external mail address and I receive it there. Thank you for your help -- Vahe --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is GNATS broken ??
On Sun, 29 Jun 2003, Vahe Khachikyan wrote: Can please somebody tell me wheter the GNATS system is OK and if somebody managed to submit a problem report last 5 days? I have sent in PRs in the last week, and there was no problem. Did your PR show up in the PR list? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universität Wien http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is GNATS broken ??
Can please somebody tell me wheter the GNATS system is OK and if somebody managed to submit a problem report last 5 days? I have sent in PRs in the last week, and there was no problem. Did your PR show up in the PR list? Nop it didn't show up in PR list. I use http://www.freebsd.org/cgi/query-pr-summary.cgi?query to query PR database. And I didn't get any ticket number per email. Any ideas ? Thanks -- Vahe --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: Re: TODO list?
Quoting Terry Lambert [EMAIL PROTECTED]: Give him a commit bit, and he can quickly grind through all the PR's that already have diff's attached to them, and have just sat there forever. I have taken a look at the PR list before, but I get depressed when I look at some of the requests. Some requests don't look very hard, but they require hardware that I don't have. How do you guys go about handling bug fixes if you don't happen to have certain hardware that someone else may have? Also, when you're working on a PR, do you roll your OS version back to whatever the PR requires? If so, do you just cvsup downgrade your source and make buildworld... etc? I have lots of interest in beginning some simple tasks with the kernel, but it's quite difficult to know where to start. I'm good at C/C++ and have taken an OS course; I just don't know how this particular kernel works on most levels. Many thanks, Mike Grim PS - Terry, I'm sorry for sending this to you directly. It was my fault for not realizing it didn't go to -hackers. - SIUE Web Mail - End forwarded message - - SIUE Web Mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: Re: TODO list?
Quoting Joseph Holland King [EMAIL PROTECTED]: heh, i must say that without a commit bit its almost impossible to get any of the pr's closed, even ones that are five years old with a fix attached. What exactly is a commit bit? I'd be willing to help him on this; I could use just as much help learning the kernel as he could. Thanks, Mike Grim PS - Joseph, I'm sorry for sending this to you directly. I should have made sure it went to -hackers. I'm just used to only hitting reply. - SIUE Web Mail - End forwarded message - - SIUE Web Mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is GNATS broken ??
At 01:45 29/06/2003 +0200, Vahe Khachikyan wrote: Nop it didn't show up in PR list. I use http://www.freebsd.org/cgi/query-pr-summary.cgi?query to query PR database. And I didn't get any ticket number per email. Any ideas ? Can you check if the mail was accepted by the FreeBSD mail server? It looks like GNATS email is rather aggressively filtered against server blacklists; I have to route all my PRs through an SSH tunnel to a different system in order to get them accepted. Colin Percival ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is GNATS broken ??
On Sun, Jun 29, 2003 at 02:18:01AM +0200, Vahe Khachikyan wrote: [...] Who knows whether the mentioned server is in blacklist ? http://dsbl.org/listing Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: TODO list?
On Sat, Jun 28, 2003 at 06:52:36PM -0500 or thereabouts, [EMAIL PROTECTED] wrote: Quoting Terry Lambert [EMAIL PROTECTED]: Give him a commit bit, and he can quickly grind through all the PR's that already have diff's attached to them, and have just sat there forever. I have taken a look at the PR list before, but I get depressed when I look at some of the requests. Some requests don't look very hard, but they require hardware that I don't have. How do you guys go about handling bug fixes if you don't happen to have certain hardware that someone else may have? Also, when you're working on a PR, do you roll your OS version back to whatever the PR requires? If so, do you just cvsup downgrade your source and make buildworld... etc? My guess is, they'll see if it's fixed on -CURRENT. I have lots of interest in beginning some simple tasks with the kernel, but it's quite difficult to know where to start. I'm good at C/C++ and have taken an OS course; I just don't know how this particular kernel works on most levels. Ditto here! -- Josh Many thanks, Mike Grim PS - Terry, I'm sorry for sending this to you directly. It was my fault for not realizing it didn't go to -hackers. - SIUE Web Mail - End forwarded message - - SIUE Web Mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
